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
Improved naming for current user variables
Value: It’s now easier to understand and use current user variables when building apps. We’ve updated how these variables are displayed in the entity browser, so their names better reflect their purpose.
This makes them easier to recognize and avoids confusion with other variables.
Impact: This feature is available for Page builder applications running on the new Pages compiler only.
Improvements & fixes
1. Fix: Box component background in Back office template
Value: This is now fixed and the Box components in the detail view of the back office template have the correct (light) background color applied, ensuring text is legible.
2. Fix: Missing pagination icons
Value: In some cases, when using the datalist, the previous/next page icons were missing. This is now fixed, and the UI is working properly.
3. Fix: Partial editor not inheriting the right component set from the page
Value: In some cases, you could only select components from the default component set when using the partial builder. The component set in partial is now reflecting correctly, the same as the component set from the page.
4. Fix: Decimal component wouldn’t allow typing of numbers in the decimal places
Value: This fix resolves some unexpected behaviour when using the decimal component.
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
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
My Betty Blocks
Improvements & fixes
1. Merge history breadcrumbs
Value: The merge history page now contains breadcrumbs for easier navigation back to the application.
Impact: Navigate to the merge history, and the breadcrumbs are displayed on the top of the page.
2. Update dashboard tiles and links
Value: The tiles link to more relevant data regarding the Academy and release notes.
Impact: Navigating to the dashboard: https://my.bettyblocks.com/
3. Applications on the NL1 zone are now able to be set to live
Value: It is now possible to set applications on NL1 to live, for governance purposes within the company overview.
Impact: Have an application running in the NL1 zone, then set the application status on the application details. This status will then also be displayed in the company overview applications page.
Education
New
Pages 101 course in Academy
Value: A modular beginner-friendly course that introduces users to Pages, showing how to create an application, set up a first page, and work with basic page components
Impact: Reduces the learning curve for first-time builders, helping them start building applications faster and with more confidence
Up next
1. SSO configuration documents: Guidance on available SSO setups, required information, and a new article on implementing Azure SSO via SAML with current SAML functions/action steps.
Timeframe: Upcoming two weeks
2. Handling unexpected action errors: Content on preventing, identifying, and solving action-building errors, plus practical error-handling strategies for builders.
Timeframe: Upcoming two weeks
3. Debugging and using Logs: Academy course on monitoring, testing, and debugging business logic with Logs, Log messages, and GraphQL playground.
Timeframe: Beginning of October
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!