Our team has focused on delivering a range of platform enhancements over the last two weeks. In this update, you’ll find a clear overview of the latest feature additions, changes, and resolved issues. For a comprehensive breakdown, be sure to review the full release notes.
Pages
New features
1. Betty Genius: Updating (parts of) generated pages (post generation)
Value: We’re introducing an upcoming feature for Betty Genius-generated pages: the ability to update specific sections of generated pages after they’ve been created. Right now, any edits to generated pages require manual changes in the page builder—a process that can slow iteration and present a learning curve for new users.
Impact: With this upcoming feature, you’ll soon be able to prompt Genius again to modify specific sections of a generated page. Simply select the part of the page you want to update, describe the change in natural language, review the suggestions, and let Betty Genius handle the update. No manual edits required.
- Quick, targeted edits: Make changes to specific page sections instantly.
- Lower learning curve: Reduce reliance on the page builder for routine edits.
- Continuity in creation: Stay in the “prompting” process and iterate faster.
2. New Pages compiler: CSP header support
Value: We are enhancing the capabilities of the new pages compiler by including CSP (Content Security Policy) headers as defined in your My Betty Blocks application settings. Previously, CSP headers were not applied when compiling pages to runtime. With this update, CSP headers will now be compiled and adhered to at runtime.
Impact: Once this feature is live, using it will require a recompile of the application with the new compiler.
Improvements and fixes
1. CompilerJS improvement:
Improved reliability of “compile Pages after merge” when using CompilerJS
We’ve made an update that increases the reliability of the “compile all pages after a merge” process when using CompilerJS. The internal consumer responsible for triggering the post-merge compilation has been relocated, resulting in improved stability and resilience during the compile workflow. This mitigation helps reduce issues where certain changes fail to appear at runtime after merging, ensuring a more consistent and predictable deployment experience.
2. New Pages compiler fix
Page builder changes could not be tested at runtime when using new Pages compiler
We’ve fixed an issue where some applications using the new Pages compiler could not see and test their page changes at runtime. This issue was caused because the Caching Service’s (in-memory) cache became corrupted and failed to reset. A permanent fix has been implemented to ensure it properly resets its memoization state and does not serve invalid metadata. This prevents the new Pages compiler from receiving incorrect information and ensures runtime behavior accurately reflects page builder changes.
3. Component set bug fixes:
- Decimal and Radio input components got cleared after a form rerender at runtime
We’ve fixed an issue that caused Decimal and Radio input components to lose their values whenever the form that they were part of re-rendered at runtime. This unexpected clearing of input values led to inconsistent behavior during user interaction. With this fix, both input types now correctly preserve their values across re-renders, ensuring stable and predictable form behavior. - New lines in Rich text editor input now save correctly
We’ve resolved an issue where the Rich text editor input component failed to preserve line breaks. Previously, pressing Enter would visually create a new line in the editor, but these line breaks were lost after saving and reloading the content. This fix ensures that all new lines are now correctly stored and displayed as expected.
4. Component set improvements:
- “Render children” option enabled by default in new Data container component
We’ve updated the default configuration of the Data container component. When adding a new Data container component to a page, the “Render children when data is present” option will now be enabled by default. Most use cases involving the Data container require this setting to be turned on. By enabling it automatically, we streamline setup, reduce manual configuration, and ensure the component behaves as expected out of the box. - Enhanced input components with adjustable “items to load” limits
We’ve introduced an improvement to the following input components: Autocomplete, Multi-autocomplete, and Select.
A new configuration option, “Number of items to load,” has been added. This setting allows you to adjust the maximum number of items(records) displayed, with selectable values of 50, 100, 150, or 200.
This enhancement provides greater flexibility when the previous default limit of 50 items wasn’t sufficient. Please note that the maximum number of 200 is enforced due to Data API page size limitations, and pagination is not currently supported for these inputs.
Several Betty Genius improvements:
- Body component update: Default background color set to “Transparent”
Every page includes an invisible Body component. Previously, this component always applied a hard-coded white background color. When using Page Layouts, the Body component is rendered inside the layout’s content area, and this forced white background often conflicted with the layout’s own background settings. To resolve these inconsistencies, the Body component’s default background color has been changed to “transparent.” This update ensures that page backgrounds now behave as intended and fully respect the layout’s design. - Requirement edits & removals are now properly saved and persisted
We’ve improved how requirement changes are handled. Edited or deleted requirements are now fully saved and persisted in the (meta) database. Previously, these updates existed only on the frontend, causing changes to disappear after reloading the requirements overview. With this fix, all requirement modifications are now reliably stored and retained across sessions. - New Modules quick menu when clicking the Modules builder bar item
We’ve introduced the Modules quick menu that appears when clicking the Modules item in the builder bar. Previously, there was no way to view Modules generated by Genius after their creation. This new quick menu now provides immediate access to your previously created Modules, improving navigation and workflow efficiency. - Show entire prompt text in requirements overview
When generating new Modules using Genius, long prompt texts were previously truncated in the requirements overview, preventing you from reviewing the complete prompt. This has now been improved: on hover the full prompt text is displayed, ensuring complete visibility of the input that generated your Module.
Up next
1. Betty Genius: Improved display of variable paths on canvas
We are improving the Pages canvas view of Genius-generated pages to provide a more consistent and readable display of variable paths in text options.
Currently, long variable paths like can break across lines or overflow their parent elements due to word-break issues, which can make the Page canvas harder to read, particularly when large heading text components are used in the Page builder.
With this upcoming update, variable paths will remain on a single line and stay contained within their parent elements, ensuring a cleaner, more consistent canvas experience. When it doesn’t fit on one line, the variable path will receive a truncated display . On hover, you will see the full variable path displayed in a tooltip.
This update will only be compatible with Genius-generated pages.
Timeframe: December ‘25
2. Betty Genius: enhanced Form capabilities
We’re improving the Form functionality in Genius-generated pages to make them more interactive and useful. Currently, generated forms include input fields but are lacking data binding and submission capabilities. With this enhancement, forms will fully support edit, create, and login user use cases.
These updates will include improvements to the Form component, all related input components, and their runtime behavior, ensuring that form data can be properly bound, submitted, and processed in an Action.
Timeframe: December ‘25
3. Betty Genius: enhanced buttons to run an action
We’re improving the Button component functionality in Genius-generated pages to make them suitable to run an action on button click. Currently, generated pages are lacking buttons that can run an action at runtime. With this enhancement, Action buttons will fully support this capability.
Timeframe: December ‘25
Actions
New features
1. Multifunctions in a custom Wasm component
- Value: Builders can upload multiple functions from a single Wasm file in one step, instead of uploading each function individually. This significantly improves the developer experience by reducing repetitive work, lowering the risk of errors, and making it easier to bring complete use cases, such as full API integrations, into projects. Additionally, it enables reusable patterns by allowing builders to package and share multifunction Wasm components via the Block Store.
- Impact: With this update, builders can efficiently import an entire set of related functions (e.g., create, read, update, delete, authentication) from one Wasm file, streamlining the setup of complex integrations. No extra steps are required beyond uploading the Wasm file containing multiple functions.
2. Ability to run a Wasm action via a Next-gen subaction
- Value: Builders can now call and execute Wasm actions directly from within a Next-gen action as a subaction. This bridges the gap between Wasm and Next-gen actions, enabling seamless interaction between the two and allowing builders to validate and reuse Wasm logic within their existing action flows. It enhances flexibility, promotes code reuse, and accelerates testing and validation of Wasm-based functionality.
- Impact: With this update, builders can easily call Wasm actions from a Next-gen action without any hurdle. This allows the usage of Wasm logic executed from a page. This is the first step in integrating Wasm actions within the platform.
3. New native functions in the Wasm action palette
- Value: Builders now have access to three additional native functions directly in the Wasm action palette: Authenticate User, Raise Error, and JSON Path. These functions were previously only available through the Block Store, but are now part of the native set in the platform, making them faster to use.
- Impact: Builders can start using these functions immediately when creating or editing wasm actions in the Actions IDE. This ensures a smoother, more streamlined workflow going forward.
If you want to try out the beta Wasm-based action builder, please reach out to lisanne@bettyblocks.com for the feature flag.
Up next
- Value: Builders will soon be able to view output generated by log steps inside their Wasm actions in the application logs. This provides insights into what happens during execution. This is the first step in bringing Wasm actions in line with the transparency and debugging capabilities available in the other actions.
- Impact: After this update, any log step added within a Wasm action will add a log message to the application logs.
- Timeframe: In the next month
2. The ability to run Wasm actions in the background
- Value: Builders will soon be able to view output generated by log steps inside their Wasm actions in the application logs. This provides insights into what happens during execution. This is the first step in bringing Wasm actions in line with the transparency and debugging capabilities available in the other actions.
- Impact: After this update, any log step added within a Wasm action will add a log message to the application logs.
- Timeframe: In the next quarter
My Betty Blocks
New features
Organization creation
- Value: Company admins can create organizations and give permissions to different company roles for organization creation, so that they can configure their own company & governance structure
- Impact: Both on the company overview with the organizations tab active and the organizations overview, users with permissions to create organizations will see an enabled create organization button.
Improvement
Resolved incorrect conflict values displayed in the Resolve conflicts view
- Value: We've fixed an issue where conflicting values were incorrectly displayed in the Resolve conflicts screen. Previously, the incoming and current change values were swapped, leading to confusion. Conflicts are now clearly presented, making it easier to review and resolve them accurately
- Impact: When using the branching functionality — such as opening the update or rebase view of a branch and accessing the resolve conflicts screen — conflicting changes are now reliably shown with the correct values, reducing potential errors during conflict resolution.
Education
New
1. Debugging actions with Log Message step lesson and video tutorial in 'Logging and debugging actions' Academy course
- Value: Gives users a practical way to understand what their actions are doing at each step
- Impact: Users can diagnose issues faster and avoid cluttered logs by choosing the right log level (Debug, Info, Warning, Error)
2. Betty Genius — Crafting a perfect prompt (video tutorial + article)
- Value: Helps users write stronger prompts that lead to more accurate generated pages and applications
- Impact: Reduces back-and-forth during generation and improves the quality of Betty Genius outputs from the first try
3. Creating an endpoint from Next-gen Actions article
- Value: Provides a clear path for connecting external systems to Betty Blocks through HTTP requests
- Impact: Developers can integrate actions into other tools, validate incoming data, and build more flexible automation
Improvements & fixes
1. Added documentation about the new ‘Inactive’ application status to:
-
Application management best practices
-
Using application status in the application development cycle
-
Application types and statuses
2. Added the Global Search feature to the Basic features of Betty Blocks article.
Up next
1. Company vs application SSO configurations: Guidance on available SSO setups - both company (My Betty Blocks) and application-level
- Timeframe: Upcoming two weeks
2. Betty Genius — Shaping your application requirements (video tutorial + article)
A new tutorial on reviewing and adjusting the generated foundation of your application in Betty Genius.
- Timeframe: Upcoming two weeks
3. Creating custom action step article: Updated explanation of the configuration process for custom action steps.
- Timeframe: Upcoming two weeks
4. Logging and debugging actions: final Academy lesson on testing your actions directly in the GraphQL playground
- Timeframe: Start of December
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!