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. Display logic option in Data table columns
Value: We’ve introduced the Display logic feature to Data table column components, enabling you to set conditional visibility for each column. With this enhancement, you can define which user roles see specific columns—for example, allowing role A to view all columns while restricting role B from seeing certain columns. Previously, this required creating multiple Conditional components and duplicating entire Data tables, resulting in complex configurations. Now, you can manage visibility directly on each column, streamlining your setup and reducing unnecessary duplication.
Impact: This enhancement is available exclusively in the newest version of the Data table column components within the default Betty Blocks component set. Existing components already implemented on pages will not be updated automatically.
2. Text area input vertical resize for better accessibility
Value: The Text area input component now supports vertical resizing, giving users greater flexibility and enhancing accessibility. This is especially useful in applications like community platforms or forums, where users often compose detailed posts or replies. With this update, users can expand the text area to match the length of their content, making it easier to write, review, and edit longer inputs without being limited by a fixed field size.
Impact: This feature is available only in the newest version of the Text area component included in the default Betty Blocks component set. Existing components already placed on pages will not be updated automatically.
3. Support for returning to referring URL after authentication
Value: The page builder now supports redirecting end-users back to their original referring URL after successful authentication. Previously, when users accessed an application through a deep link (e.g., “betty.app/home/project/project:id”), that original URL would be lost after authentication. This required clunky workarounds, often disrupting user experience and breaking end-user activity tracking in customer dashboards. With this enhancement, the referring URL is preserved during authentication, ensuring users seamlessly land on their intended page while maintaining accurate analytics.
Impact: This feature is compatible with applications running on the new pages compiler only.
Improvements & fixes
1. Updated page variable filtering
Two weeks ago, we updated the filter component option. Now we have updated the page variable filtering, available when editing or creating a page variable. While the primary focus of this update was a technical refactor, we've also taken this opportunity to update the UI and UX—making it a bit easier and more intuitive to define filters.
Page variable filter - What has changed?
- Wider modal: The default max width of the create and edit variable modal has been increased, giving more space for complex filter configurations.
- Smarter rule creation: When adding a new filter rule, the entity browser now opens automatically to help you quickly select properties.
- Improved predicate selector: We've replaced the browser’s default predicate selector with a styled dropdown for better consistency and usability.
- Retained values on predicate change: Changing the predicate no longer resets your selected value on the right-hand side, making editing faster and less frustrating.
- Better button placement: The Apply and Cancel buttons now appear at the bottom right of each filter rule, aligning with the left-to-right configuration flow.
- One rule editing at a time: You can now only edit one filter rule at a time. Opening another rule while one is being edited will cancel the unsaved changes of the previous rule—preventing conflicting updates.
- Clear error handling: If a referenced item in a filter is missing (e.g., due to deletion), both the filter option and the specific rule now show an appropriate error message (e.g., “Property not found”).
- Reference renames handled: When used references are renamed, those changes are now properly reflected after a refresh to all items. This wasn’t the case before.
- Password property: Password properties can no longer be selected on either side of a filter rule, since there's no valid use case for this.
- Enhanced "has-many" filtering: When filtering through a has-many relationship, the "includes" and "does not include" predicates appear. The accompanying token input on the right-hand side has been improved for both editing and reading states.
2. Fix: Password input icon customization
Value: The Password input component has been updated to resolve issues with the visibility toggle icon. Previously, the icon could not be changed, removed, or styled, meaning that adjustments to the icon option, positioning, or color had no effect. These issues have now been fixed, allowing full control over customizing or removing the icon as intended.
Impact: This update will only be available in the latest version of the Password component in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
3. Fix: Filter component height and width adjustments in design time
Value: The Filter component now correctly reflects changes to its height and width during design time. Previously, updates to these options had no direct effect on the component’s appearance in Pages, causing inconsistencies between configuration and layout. This issue has been resolved, ensuring that size adjustments are immediately visible and accurately represented.
Impact: This update will only be available in the latest version of the Filter component in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
4. Fix: Input components helper text and placeholder text adjustments in design time
Value: All Form input components from the default component set now correctly reflect changes to their helper text and placeholder component options during design time. Previously, updates to these options had no direct effect in Pages, causing inconsistencies between configuration and layout. This issue has been resolved, ensuring that helper text and placeholder text are immediately visible without a browser refresh.
Impact: This update will only be available in the latest version of the Form input components in the default Betty Block component set. Existing components already in use on pages will not receive this update automatically.
5. Fix: Number input scrolling behavior at runtime
Value: The Number input component has been updated to fix an issue that occurred when scrolling inside the input while it was focused at runtime. Previously, scrolling would change the component’s internal value without updating the visible typed value, leading to mismatched data and unexpected numbers being submitted. This issue has now been resolved, ensuring consistent and reliable input behavior for end-users.
Impact: This update will only be available in the latest version of the Number input 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: August 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: August 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 end of August
Actions
Improvements & fixes
1. References of Actions with Pages
Value: Builders can now directly navigate from an action to its connected Pages component. Previously, when an action was linked to a Pages component, it couldn’t be deleted, but there was no clear way to trace back to the specific page or component. This enhancement provides transparency and saves time, helping builders quickly understand where and how an action is being used.
Impact: This enhancement is directly available for every action.
2. Return button from Actions to Pages
Value: Users navigating from the page builder to an action can now easily return to their original page with the re-implemented Return button. This resolves the frustration of losing context when switching between actions and pages, ensuring a smoother and faster workflow for builders.
3. Block Store search in Actions
Value: Due to maintenance, the Block Store search in the palette of an action was temporarily not functional. This has been fixed.
Up next
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
Timeframe: Within two weeks
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!