Over the last two weeks, we have been working on improvements to the platform. This blog post provides a simple list of what has been changed and updated and what bugs have been fixed. You can read more about the release notes here.
Pages
New features
1. Current user variables
Value: Accessing logged-in user data on Pages is now simpler and more powerful. Instead of relying on data container components, authentication profile variables (representing the logged-in user) are now automatically available across all Pages. You can now seamlessly use current user variables in the following scenarios:
- Pages: Reference these variables on pages
- Partials: Reference these variables on partials.
- Data components filter: Use these variables on the right-hand side of these filters (as values)
- Page variable filter: Use these variables on the right-hand side of these filters (as values)
Impact: This feature is available for Page builder applications running on the new Pages compiler only.
2. Data components filter on variables
Value: We’ve expanded the power of page variables by allowing them to be used on the right-hand side of data component filters (as values). This makes it easier to connect your data displays with dynamic values available on the page. You can now filter data components, such as tables or lists, using page variables or current user variables. For example:
- Render a table of Projects filtered by a Client object variable fetched on the page.
- Render a list of Projects filtered by the Current user variable fetched on the page.
Impact: This feature is available only for the page builder applications running on the new Pages compiler.
3. Filter variables on variables
Value: We’ve expanded the power of page variables by also allowing them to be filtered by other page variables (as values on the right-hand side).
Impact: This feature is available for Page builder applications running on the new Pages compiler only.
Display logic for Tab сomponents
Value: The Display logic option is now available at the Tab level within a Tabs component. This allows you to define show-and-hide logic for individual tabs, giving you more control over role-based or context-based user experiences.
Use-case example: Consider an application with a project workspace detail page that is accessible to both internal users and client users. The page includes several tabs:
- A Workspace Overview tab, visible to all users.
- A Client Documents tab, showing files uploaded by the client.
- An Internal Documents tab, restricted to internal users only.
With the new Display logic option provided, you can easily control which tabs appear for which users. For example, the Internal Documents tab can be hidden from client users while remaining visible to internal staff. This enables personalized, role-specific navigation without the need to duplicate pages or create separate components.
Impact: This update will only be available in the latest version of the Tab components in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update
Improvements & fixes
1. Fix: Unable to filter tables on date picker input
Value: The Date picker input component has been updated to resolve an issue when using the filter interaction on tables or lists. Previously, you received a query error in the data component when filtering. This has been fixed now, allowing you to use filter interactions with date pickers again.
Impact: This update will only be available in the latest version of the Date picker component in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
2. Fix: Filter option V2 bug when using authentication profile properties
Value: The Filter option V2 (recently released) has been updated to resolve an issue when using authentication profile properties on the right-hand side of the filters. Previously, saving such filters wasn’t stored correctly, resulting in a non-resolving filter query at runtime. This has been fixed now. Allowing you to use authentication profile properties in Filter options again.
Impact: Users do not need to take any additional steps to benefit from this.
3. Improvement: Form components with extra default interactions
Value: We have updated all form components with the addition of extra default interactions on adding these components to the canvas. The extra interactions should prevent double submission of forms, by on-action loading, disabling the Button and toggling the Button loading state. Previously, the Form components received these interactions:
- On action loading, hide the success alert component
- On action loading, hide the error alert component
- On action success, show the success alert component
- On action error, show the error alert component
With the latest update, these extra interactions are added to the form components by default:
- On action loading, toggle button loading state option
- On action done, toggle button loading state option
Impact: This update will only be available in the latest version of the Form components in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
Up next
1. New filter user interface implementation
- Value: We’re introducing a new and improved filter interface throughout the Page builder, enhancing both the user experience and technical maintainability. Filters are used in three key areas — data components, page variables, and display logic. While primarily a technical refactoring, this release also includes a refreshed UI and improved UX for easier and more efficient filtering.
- Impact: Users will experience a new UI for filters, while the underlying metadata to the backend remains unchanged. There should also be zero impact at runtime because of this. We will be starting with switching to these new filters in data components, followed by page variables and display logic.
Timeframe:
-
- Data components filter option: Released
- Page variables filter: Released
- Display logic filter: September 2025
2. Toggle form changes syncing per action step
- Value: This feature will allow developers to enable or disable form change synchronization for individual action steps that include the 'value mapping' step option type, like the default Betty Blocks create and update steps.
- Impact: This option enables the new time-saving synchronization feature to be applied to older forms. It allows you to synchronize form changes across multiple action steps simultaneously and provides the flexibility to disable the synchronization feature when it is not needed.
Timeframe: September 2025
3. Page layouts
Value: We are introducing new page layouts in Pages, a feature that explicitly separates the Layout and Body sections of a page, the two fundamental building blocks of any application page.
With page layouts, you can define multiple reusable layouts (for example, with different headers, navigation, or footers) and assign a single layout to each page. This brings significant benefits:
- Reusability – build once, apply across multiple pages
- Consistency – ensure a uniform look and feel throughout the application
- Scalability – manage and evolve layouts independently from page content
Impact: This feature will only be compatible with applications running on the new pages compiler
Timeframe: September 2025
Models
Up next
Improving the current setup of Wasabi
- Value: We will be improving our current subaccounts and buckets setup of Wasabi Technologies to improve the performance of storing the assets. This change is part of our continuous efforts to optimize our services and ensure we leverage the most efficient and secure solutions available.
- Impact: No action is required nor expected from our users
Timeframe: Continuous releases till the middle of September
Actions
New feature
Unlock high-code capabilities with the Wasm-based action builder
- Value:
- Unlocking high-code flexibility within low-code: By enabling high-coders to visually model Wasm components, Betty Blocks can bridge the gap between the perceived limitations of low-code and the flexibility of high-code. This enables developers who desire more control and customisation within a low-code environment.
- Breaking vendor lock-in: The ability to export Betty Blocks actions as Wasm components provides customers with the significant value of application portability. This means their actions are no longer tied solely to the Betty Blocks platform and can potentially be run elsewhere, increasing customer freedom and reducing concerns about vendor lock-in.
- Expanding code language support: The feature's potential to transform code written in various languages (Rust, Python, etc.) into Wasm opens up the Betty Blocks platform to a wider range of development skills and project types, breaking the limitations of proprietary low-code technologies.
- If you want to try out the Beta Wasm-based action builder, please reach out to lisanne@bettyblocks.com for the feature flag. What you will unlock with this feature flag:
- Create a Wasm action via the Actions IDE
- Feature: Choose the Wasm type when creating an action
- Value: Enable the new Action Builder that allows you to build Wasm components in a low-code environment
- Upload your custom Wasm components
- Feature: Expand your action builder with custom Wasm components / functions, written in your preferred language.
- Value: High-code developers can build advanced, performance-critical components in any WebAssembly-supported language, such as Rust, Java, or Python. These components are brought into the platform as visual, reusable building blocks. Low-code developers can configure and orchestrate them using familiar drag-and-drop tooling, without writing a single line of code.
- Download your Wasm binary
- Feature: The ability to download the .wasm binary file and source code to inject this business logic into your high-code projects.
- Value: Add high-code logic to low-code apps with the upload, or extend high-code projects with low-code components.
- Create a Wasm action via the Actions IDE
Education
New
Troubleshooting for on-premise
Added a troubleshooting guide for on-premises setups, helping users quickly resolve common app creation issues and reduce downtime
Improvements & fixes
The following articles now include updated guidance on using color and spacing options:
Up next
1. On-premise SSO configuration
This article outlines how to configure SSO and user provisioning for secure, efficient access management in on-premise environments.Timeframe: upcoming 2 weeks
2. Logs & error handling
A video guide on using logs, the Log message action step, and debugging techniques within Betty Blocks.
Timeframe: mid-September
Platform roadmap
Want to know more about the upcoming features and functionalities of the Betty Blocks platform? Visit the platform roadmap of our community, where you can find most of the topics that we are currently working on and are planning to work on. Let us know your thoughts by upvoting the topics you believe are the most valuable!