Release notes - April 2026.9
List of release notes from April 29, 2025
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. App Blueprint
A new platform feature that gives you an overview of how all parts of your application are connected. It provides a high-level schematic view of your app today and is designed to grow into an environment where you can also plan, build, and evolve application components.
The very first version includes the following scope:
-
Visualize all the pages that make up your application
-
See which page layouts are in use and which pages they’re applied to
-
Visualize how pages and Layouts are connected via navigational components, such as menu items or navigation buttons inside a page.
In this schematic view, we will eventually also allow you to preview your Genius AI chat proposals and saved Plan next to your existing application parts.
2. Betty Genius: Collection pagination controls
In Genius-generated Pages, you will be able to control the skip and take and the current page of a collection of records. This allows you to generate or build manual pagination controls for data tables or data lists, including a descriptive text as "1 to 20 of 100 total results" dynamically displayed, with a next and/or previous 'page' button.
3. Betty Genius: Collection Total count property
In Genius-generated Pages, you can now display the total number of records present in a collection. Typically used inside the header title on top of a data table and in data table or list pagination controls.
4. Betty Genius: New components supported
Genius-generated Pages will include the following new components:
- Popover component – a button that, when clicked or tapped, opens a small dropdown with a list of options. Commonly used in menus or data tables.
5. Betty Genius: Filter collection variables 'on Blur' or 'on Button click'
In Genius-generated Pages, you can use input components to filter collection variables used in data tables or lists. Previously, filters were applied as soon as an input changed at runtime; now you can also apply input values on blur or via a button click (for example, an “Apply filter” button).
6. Betty Genius: Snackbar auto hide event
The Snackbar components in the Genius component set now support an auto-hide interaction event. Use this to automatically hide a Snackbar after a specified duration, configured as an option on the component. Provide the duration in milliseconds, and it will be applied at runtime.
Improvements & fixes
Betty Genius bug fix
Forms unintentionally using collection variables
In Genius-generated Pages, Edit Forms are expected to receive an object page variable for the loaded record from the database. In some cases, however, Genius AI incorrectly assigned a collection variable instead of an object variable, resulting in an invalid configuration. We’ve now fixed this behavior and updated the IDE, so this option is no longer allowed.
Betty Genius bug fix
Removing Form schema properties unintentionally
In Genius-generated Pages, we’ve fixed a bug where using the Form input property option could unintentionally remove a form schema property. Previously, duplicating a Form input and then clearing the property on the copied input would also remove the schema property from the original input. This behavior was incorrect: clearing a property should first verify whether other inputs still rely on the same underlying schema property. This is now resolved, so you can safely duplicate configured inputs in Genius-generated Forms.
MUI component set bug fix
Multi-autocomplete input not sending value after search
In the MUI Multi-autocomplete component, we’ve fixed a bug that occurred when sending a value after using the search input. Previously, the component stopped sending the correct value once you searched. This is now resolved. To benefit from the fix, ensure you are using the latest version of the component on your canvas.
Page builder bug fix
Detail view toggle in Back office page template
We’ve fixed an issue with the toggle option for opening the detail view in the Back office template. Previously, the toggle stopped responding in the page builder (design-time only). This is now resolved.
Up next
1. Betty Genius: New Genius components supported
Genius-generated Pages will include the following new components in the Genius set:
-
File upload input component – allows end users to select and upload a file from their device to the application.
-
Autocomplete input component (with search) – opens a dropdown with available options, including inline text search, to select a single option.
-
Multi-autocomplete input component (with search) – lets users select multiple options, supported by inline text search.
-
Multi-select input component – lets users choose multiple options from a list instead of just one, often displayed with checkboxes, chips, or cards.
-
Tabs component – lets users switch between different sections of content within the same view without navigating to a new page.
Timeframe: May '26
2. Betty Genius: Dialog enhancements
In Genius-generated Pages, using dialogs will be enhanced with:
- Set record context from a data table to the object page variable used in a dialog
- On closing a dialog, reset the form fields to their initial (default) values
Timeframe: May '26
3. Betty Genius: Displaying sub-collections in Pages
In Genius-generated Pages, you will be able to display sub-collections (Has-many or Habtm relationships) directly within both data table columns and record detail views. This enhancement makes it easy to surface relational data inline, without additional configuration or workarounds.
Typical use cases include:
- Displaying a project’s Labels directly within a Projects data table.
- Showing a list of Labels within a Project detail view.
Timeframe: May '26
4. Betty Genius: External dependencies support in Genius components
We are introducing support for external dependencies within Genius components, enabling the use of third-party libraries directly inside the Genius component set. This will allow us to ship more powerful, feature-rich components, such as a Google Maps component, that rely on established external libraries while remaining fully integrated within the platform.
This capability is also designed to extend beyond platform-provided components. In the future, users will be able to leverage the same mechanism to incorporate external dependencies into their own components, similar to what is already possible with the MUI component set.
Overall, this unlocks a new level of flexibility and extensibility for building advanced, production-ready UI components within Genius.
Timeframe: May '26
5. Filtering collections using Multi-autocomplete inputs
In Genius-generated Pages, you’ll be able to filter collection variables on Habtm or Has-many relationships using values selected in a Multi-autocomplete input component. This unlocks powerful relational filtering scenarios—for example, using a Roles Multi-autocomplete input to dynamically filter a Users data table. You can configure the Users collection to return records that match any or all of the selected Roles.
Timeframe: May '26
6. Betty Genius: new Text filter predicates – Is empty & Is not empty
In Genius-generated Pages, page variable filtering and display logic filtering will be supported with two new Text filter predicates: Is empty and Is not empty. These predicates make it easier to query or control content visibility based on whether a Text property has a value.
Example use cases:
- Show the Last Name text field only if First Name has a value (Is not empty).
- Display an information panel only if Email has no value (Is empty).
Expected behavior of is empty and exists on Text fields compared:
- Is empty / Is not empty – Checks whether a Text field has content.
""orNull→ Is empty"Hello"→ Is not empty
- Exists / Does not exist – Checks whether a Text field is defined (not null).
""or"Hello"→ ExistsNull→ Does not exist
Timeframe: May '26
7. Betty Genius: Automated Form action step syncing
We are introducing automated syncing between Forms and their associated action steps in Genius-generated Pages. Today, when forms in Genius-generated Pages are modified, related action steps (such as Create or Update Record steps) do not automatically reflect those changes, requiring manual updates.
With this upcoming enhancement, any changes made to a form (such as adding, removing, or updating inputs) will automatically be synchronized with the corresponding action steps. Field mappings will stay aligned without additional configuration.
This will make working with Genius-generated Pages more seamless and consistent with classic Pages, significantly reducing manual maintenance and ensuring form-driven workflows remain accurate as they evolve.
Timeframe: June '26
Actions
New features
1. Inherit authentication profiles from MCP folders
- Value: Building on the latest release's API Key authentication for MCP servers, authentication profiles set on an MCP folder are now inherited by every action inside that folder. This removes the need to set authentication per action and prevents drift where one action in a server is configured differently from the rest.
- Impact: Set the API key authentication profile once at the MCP folder level and every action inside automatically picks it up. Action permissions and the public/private state are derived from the folder via the Meta API. If an action in an MCP folder does not have the same auth profile as the folder, it is automatically removed from the MCP tools so authentication mismatches no longer leak into runtime. The action icon in the IDE also reflects the folder's permissions.
- Value: Application configurations (API keys, secrets, etc.) can now be referenced directly inside the actions of an MCP server, removing the need to hard-code sensitive data and enabling DTAP-specific MCP server keys.
- Impact: Reference any Betty config from within an MCP server action at runtime. Sensitive values stay centralised in the app configuration and flow through to the action automatically.
- Value: Debugging a Wasm action no longer requires jumping out to a separate logging tool. A direct "Show logs" entry point is now available from the action itself, giving builders one-click access to runtime output.
- Impact: Open any Wasm action in the IDE and use the new Show logs button to inspect what happened during the most recent runs — useful for tracing errors, verifying inputs, and checking step-by-step behaviour.
- Value: Custom Wasm components are no longer limited to a single function per upload — one component can now expose multiple functions, which better matches how component authors actually structure their code.
- Impact: When uploading a Wasm component with the CLI, all exported functions are picked up automatically and made available as separate steps in the action builder.
Improvements & fixes
1. Wasm Actions stability fixes
- Value: A batch of long-standing Wasm action bugs have been resolved, removing several confusing failure modes that builders and tech support hit repeatedly.
- Impact: Fixed the empty
500error from simple Wasm actions, the400error reporting "object 'onecall' is not found", the spurious "Action could not be found" error, the internal server error when assigning an empty collection to a relation, and the missing return-url button when redirecting from Pages to the action builder. The Wit files in the Actions Compiler have also been adjusted so every component can be upgraded to the latest version.
- Value: The API key authentication profile flow introduced in the last release now handles edge cases properly, so builders cannot get stuck in an inconsistent state.
- Impact: The Data API compiler no longer fails when an API key auth profile is in use; deleting an auth profile that is still referenced now produces a clear error instead of silently breaking compilation; authorization is correctly enforced for actions in a private MCP folder; and compilation no longer fails for actions in draft inside an MCP folder.
Up next
Connect your own GitHub repository to Wasm Actions
- Value: Developers will be able to bring their own codebase into the Wasm Actions IDE, enabling full control over versioning, collaboration, and code reuse across teams. This removes the limitation of only using the Block Store and opens up more advanced development workflows. Teams can align with existing GitHub practices such as pull requests and code reviews, increasing flexibility and making it easier to scale and maintain complex logic.
- Impact: Users will be able to add a link to a GitHub repository in the list of repositories in their My Betty Blocks environment and use it as the source for their functions. After connecting, functions can be selected and used in actions similar to how Block Store functions are used today.
- Timeframe: Date to be decided.
My Betty Blocks
Improvements & fixes
1. FusionAuth rolled out to all applications
-
Value: FusionAuth is now enabled for all applications.
-
Impact: Stronger, more flexible identity layer for apps with no per-app setup overhead.
2. Branch delete reliability
-
Value: Deleting a branch on the same level now works as expected.
-
Impact: Removes a small but persistent annoyance for teams managing branching workflows.
3. App creation from a template
-
Value: Creating an app from a template no longer fails when the template references a missing file.
-
Impact: Template-based app creation is more forgiving. Missing files are handled gracefully instead of breaking the whole flow.
4. Database performance
-
Value: Indexes on the tables were improved.
-
Impact: Queries that hit these tables run faster, reducing latency on metadata operations across the platform.
Up next
Smarter rebase for deleted items
-
Value: Rebasing branches will resolve conflicts caused by deleted items more cleanly.
-
Impact: Fewer manual merge headaches when branches diverge, especially when items have been removed on one side.
-
Timeframe: April 2026
Education
New
1. Dynamic redirect after login based on user role
Added a new article covering how to redirect users to different pages after login based on their role. It walks through a no-code approach using the Redirector page and briefly covers a pro-code option using a custom interaction for developers who want a cleaner flow.
This guide walks you through installing the wash CLI and pulling the Wasm file you need to add an action step to Betty Blocks.
Improvements & fixes
Page security (for a specific users & roles)
Fixed the Securing a page (for one or more in-app roles) guide to reflect the current configuration steps.
Up next
Betty Solutioneer documentation
- Value: A new article explaining what Betty Solutioneer is, where to find it, and how to use it to turn a business case into a structured analysis ready for app building
- Impact: Business users get a clear reference for the feature instead of figuring out the flow on their own
- Timeframe: Upcoming 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!