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: Generate options for navigation between pages
Value: Betty Genius now automatically creates navigation links — such as menu items and buttons — between generated pages in multi-page generation. This improvement improves navigation setup, making layouts and pages ready for use immediately after generation. Users can instantly click to move between pages like Home and Projects with no additional configuration required
Impact: Betty Genius is available by signing up for a trial from the Betty Blocks website. If you want to make use of this in your existing application, please reach out to our Customer Success team.
2. Betty Genius: Data model with dummy data generation
Value: Multi-page generation now includes automatic creation of Detail and Edit pages with filtered object variables. Instead of manual setup, Betty Genius configures the necessary input variables and filters, so only relevant data appears on each page.
With this enhancement, users benefit from:
- Context-specific data display on Detail and Edit pages
- Reduced setup time and less manual data-binding work
Impact: Betty Genius is available by signing up for a trial from the Betty Blocks website. If you want to make use of this in your existing application, please reach out to our Customer Success team.
Improvements and fixes
1. Component set improvement: number of items(records) flexibility
Value: We’ve enhanced the Autocomplete, Multi-autocomplete, and Select components with a new configuration option: “Number of items to load.” You can now set the maximum number of items (records) displayed to 50, 100, 150, or 200 — giving you greater flexibility when working with larger data sets. The maximum limit of 200 items is in place due to Data API page size constraints, and please note that pagination is not yet supported for these component inputs.
Impact: This update will only be available in the latest components version in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
2. Betty Genius improvement: hidden ‘Models’ tab in entity browser
Value: To simplify and focus the entity browser when updating component options, the ‘Models’ tab has been removed. This tab previously listed models from data components (like data containers), but since Genius pages no longer use these components, the tab remained empty. With this update, the page variables tab is now the default and first visible tab, creating a more focused editing experience.
Impact: Users do not need to take any additional steps to benefit from this
3. Betty Genius has several bug fixes:
We’ve resolved several bugs affecting Genius-pages to improve overall stability and user experience:
- Deleting layouts caused a redirect loop. It now correctly redirects back to the Pages overview.
- Login pages were incorrectly generated as “empty” pages.
- Fixed an issue where some pages were marked as “done” before they were actually complete.
- Corrected an issue where images were not always displayed during page generation preview.
- Fixed a bug where the Data tab incorrectly displayed (0) models after requirements generation.
- When generating pages, the requirements section pushed the 'Pages' list off-screen.
- Fixed misaligned columns in data tables during the design time of generated pages
4. New Pages compiler fix: Remote model data formatting
Fixed an issue where number and price formatting were not correctly applied at runtime when using Remote Models (from Data Sources) on Pages. The new pages compiler now properly applies formatting for remote model data as expected.
Impact: This fix is compatible only with the new pages compiler and requires recompiling the application with it.
Up next
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.
Timeframe: November ‘25
2. New Pages compiler: CSP header support
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.
Timeframe: November ‘25
3. Page Builder canvas view: Improved display of variable paths on canvas
Value: We are improving the page builder canvas view to provide a more consistent and readable display of variable paths in text options. Currently, long variable paths can break across lines or overflow their parent elements due to word-break issues, which can make the interface harder to read, particularly when large heading text components are used in the Page builder.
Impact: 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.
Timeframe: November ‘25
Actions
New features
1. Create, update and delete capabilities in Wasm Actions
- Value: Builders will soon be able to implement create, update, and delete operations directly within Wasm Actions. This enhancement extends the functionality of Wasm Actions to match the capabilities of Next-gen Actions, marking a significant step toward a more robust and adaptable actions engine. With this update, builders can efficiently manage the entire action lifecycle in a unified, Wasm-powered environment.
- Impact: Once the feature flag is enabled, builders can create Wasm actions with the Create, Update and Delete steps.
2. Set the Wasm action to private
- Value: Users will be able to set their Wasm action from public to private, select an authentication profile and configure the roles that can perform the action.
- Impact: Once the feature flag is enabled, users can set their Wasm actions to private.
Improvements & fixes
Display Wasm actions in the Action overview tabs
Value: Wasm actions are now visible in the All, Authenticated, and Public tabs within the Actions overview. Previously, these actions were not displayed in these tabs.
Impact: Builders automatically benefit from this improvement—no additional configuration is needed
Up next
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.
- Timeframe: Upcoming 2 weeks
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.
- Timeframe: Upcoming month
3. 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.
- Timeframe: Upcoming quarter
Education
New
1. Building with data – Academy course
- Value: A new Academy course that helps users understand how to structure and use data in their applications
- Impact: Users can now learn the fundamentals of data modeling and practice connecting their data to pages using Data components, improving how they build data-driven applications
2. Connecting with OneSignal for push notifications
- Value: A new guide explaining how to integrate the OneSignal service for app push notifications
- Impact: Developers can now easily set up and test push notifications, enabling better communication with end users directly through their applications.
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
3. Debugging and using Logs: Academy course on monitoring, testing, and debugging business logic with Logs, Log messages, and GraphQL playground.
- Timeframe: End of November
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!