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: store the value of a Multi-autocomplete in a page variable
In Betty-genius Pages, a new custom collection page variable type lets you capture the values selected in a Multi-select or Multi-autocomplete component and apply them to filter a data table only when Apply filter button is clicked. This gives you control over when a multi-select input for filtering is actually applied, instead of filtering on every selection change.
2. Betty Genius: Set values interactions can now target component state
In Betty-Genius Pages, the Set variables interaction has been renamed to Set values and can now assign values directly to a component's state, not just page variables only. Each input's default value option is also exposed to page state, so it can be reset back to its default. This feature unlocks to build "reset filters" button click functionality without extra configuration. On click of the button component, you are able to set the value of each filter input back to their initial (default) value again.
Improvements & fixes
Betty Genius improvement
Action output types now match their actual return value
In Betty-Genius Pages, when creating an action reference, the default output key's type now matches the value type actually returned by the action's Finish step, instead of always defaulting to Text.
- Value: Removes the need to manually correct the output type after creating an action reference.
- Impact: Reduces type-mismatch errors when using action outputs elsewhere on a page.
Betty Genius improvement
Improved reliability of Genius-generated pages
Betty Genius was generating tables and lists with unnecessary or misplaced collection wrappers, and some generated apps contained navigation buttons pointing to invalid or non-existent pages.
-
Value: AI-generated pages now come out with a cleaner component structure and working navigation.
-
Impact: Reduces manual cleanup needed after generating a page or app with Genius.
Betty Genius bug fix
Fixed page-level redirect and display logic issues
A page-level redirect interaction using an On data condition check was redirecting every time, even when the condition was false. Separately, display logic combining a page variable with a field from a nested sub-collection could crash the page at runtime.
- Value: Redirect and display-logic conditions now behave as configured.
- Impact: Prevents users from being incorrectly redirected or landing on a broken page.
Betty Genius bug fix
Fixed data integrity issues when duplicating Genius pages
Duplicating a Genius-generated page could lose collection variable references, break object-variable filters, drop a form's custom object variable, and leave duplicated actions pointing at the original page's schema instead of their own.
- Value: Duplicated pages now come with their own independent, correctly configured variables and schemas.
- Impact: Prevents subtle data and configuration bugs from carrying over into duplicated pages.
Betty Genius bug fix
Fixed default values and validation on input components
Several input types didn't load their configured default value until a user manually changed them, standalone inputs placed outside a form didn't show default values or toggle correctly, and radio inputs had multiple issues with independent selection, required validation, and display logic.
-
Value: Inputs now show and validate their default values correctly from the moment a page loads.
-
Impact: Reduces confusing form behavior and data entry errors for end users.
Up next
1. Betty Genius: Login and Logout interactions
In Genius-generated pages, the Login and Logout interactions for custom created authentication profiles will be supported. This allows you to build these login flows with the use of the Genius component set instead of using the fallback of the MUI component set.
Timeframe: July '26
2. Betty Genius: Redirect to URL returned in action response
In Genius-generated pages, the Redirect interaction will be supported to target a URL returned from an action response instead of only a fixed internal or external page. Choose Internal or External, pick the property via the entity browser (Text, URL, File, or Image), and select current or new tab. Works for both page-level and component-level interactions. This will enable dynamic redirects, like downloading a freshly generated export or sending users to different pages based on role after login.
Timeframe: July '26
3. Betty Genius: New Genius components supported
Genius-generated Pages will include the following new components in the Genius set
- Tabs component – Lets users switch between different sections of content within the same view without navigating to a new page.
- Stepper component – Guides users through a multi-step process in a defined sequence, displaying progress and allowing navigation between steps such as form wizards, onboarding flows, or checkout processes.
- Responsive layout components - A set that automatically adapts to different screen sizes and viewports, enabling consistent and fluid designs across different screens.
- Progress bar component - Visually communicates the completion status of a task or process, showing users how far along they are as a filled bar that advances from 0% to 100%.
Timeframe: July '26
4. Betty Genius: other custom collection page variable use cases
In Genius-pages, a new variable type will be supported: custom collection variable. This unlocks the following use cases:
-
Selecting multiple rows in data tables collection to run batch actions (e.g. Update the status property of the selected records from the table).
-
Build forms that store a collection of objects in local page state before submitting them to an action. For example, an event registration form where users can add one or more visitors as part of a single form submission.
Timeframe: July '26
5. 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: August '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: August '26
Actions
New features
1. Run actions in the background for longer tasks
- Value: Wasm actions can now run in the background for more than 10 minutes, instead of only completing short, synchronous runs. This opens up use cases like remote data imports or generating and emailing large PDF files.
- Impact: Live now in a first set of environments. No action needed. More environments follow later this year (see "Up next").
2. AI actions agent: build CRUD and integration actions
- Value: The actions agent can now generate CRUD actions and API/HTTP integration actions from a prompt, so you no longer need to build them by hand.
- Impact: Available wherever the actions agent is enabled. This adds to existing functionality — no rebuild needed.
Improvements & fixes
1. Popover: new spacing and dismiss options
- Value: More control over the Popover component — set the spacing around it and let users dismiss it with Escape or a click outside.
- Impact: Both options are optional and don't affect existing popovers. No rebuild needed.
2. New "up/down" icon
- Value: One more icon added to the core icon set.
- Impact: Available immediately in the icon picker.
3. Bulk create, update, and delete in the Data API component
- Value: The Data API component now supports bulk actions, so high-volume actions run faster.
- Impact: Use the new Upsert-many and Delete-many operations. File properties and has-and-belongs-to-many relations aren't supported yet when creating records this way.
4. Fixed: list properties in IDE models
- Value: Three bugs that could cause list properties to lose or fail to save values when switching or editing them are now fixed.
- Impact: No action needed.
5. Fixed: PDF property errors on-premise
- Value: Generating PDFs through the PDF property no longer fails with a storage error on on-premise environments.
- Impact: No action needed.
6. Fixed: Wasm actions becoming unavailable
- Value: Wasm actions and MCP servers no longer stop responding after running for a while.
- Impact: No action needed.
7. Fixed: debug logging errors
- Value: Debug logging no longer fails when many variables are logged at once.
- Impact: No action needed — variables are grouped automatically to prevent this.
Up next
1. Background actions: wider rollout
- Value: More environments gain access to background, long-running actions.
- Impact: No action needed ahead of release.
- Timeframe: Rolling out to additional environments. Date to be decided.
2. Wasm component discovery and catalogue
- Value: Discover and import Wasm components published outside your own app.
- Impact: Currently behind a feature toggle. No action needed yet.
- Timeframe: To be decided.
3. On-premise security hardening
- Value: Improved security posture for on-premise environments.
- Impact: No action needed.
- Timeframe: To be decided.
My Betty Blocks
New features
1. Software and application catalog for company admins
- Value: Company admins get a full overview of their organization's applications and integrations, including who owns each one, instead of no central view at all.
- Impact: Available in My Betty Blocks, currently behind a feature flag. Admins can view and edit catalog entries and assign application owners from users within the same company.
Note: Request feature flag via this email: anton.vandenberg@bettyblocks.com
2. Automated DNS and route management for on-premise environments
- Value: On-premise customers can now manage custom domains, routes, and SSL certificates directly through the platform, instead of setting these up manually.
- Impact: Available through My Betty Blocks' custom ingress management. Supports PEM and PKCS#12 certificate formats; certificates link automatically to the correct route. DNS verification is skipped where not needed on-premise.
3. File properties in trial zones
- Value: You can now create file properties while working in a trial zone.
- Impact: Available immediately, no action needed.
Improvements & fixes
1. Fixed: Blocks page table width
- Value: The table on the Blocks page now fills the available space instead of leaving it partly empty, including when expanded.
- Impact: No action needed.
2. Fixed: import error on application upgrades
- Value: Importing or upgrading applications no longer fails with a configuration error on affected environments.
- Impact: No action needed.
3. Fixed: blocked app assets on some networks
- Value: App files such as templates and stylesheets are now served from a Betty Blocks domain instead of a third-party storage URL, so apps no longer break for users whose network blocks that provider.
- Impact: No action needed, applied automatically.
4. Fixed: underscores in naming
- Value: Naming that includes underscores no longer breaks after a recent platform infrastructure update.
- Impact: No action needed.
5. Fixed: deleting organizations with connectors
- Value: Organizations with connectors attached can now be deleted, instead of the action failing.
- Impact: No action needed.
Up next
1. Software catalog: roles and permissions
- Value: Access to the software catalog will be controlled by roles and permissions instead of being limited to global admins only.
- Impact: No action needed ahead of release.
- Timeframe: To be decided.
2. DNS and route automation: wider rollout
- Value: More on-premise customers get automated DNS, routing, and SSL management.
- Impact: No action needed ahead of release.
- Timeframe: To be decided.
Education
New articles
Variables topics were among the most searched-for terms in our docs, but the information lived in a few articles that was hard to scan. We've split it into three focused articles, so you can find the answer you need faster and get a clearer explanation of each variable type.
Improvements & fixes
A sandbox is a copy of your application in which you can make changes without making these changes directly in your live application.
Up next
1. New environment for Betty Blocks Documentation
We're working on a new, updated docs format powered by AI — giving you instant answers instead of manual searching.
Timeframe: End of July '26
2. Registration request for Academy
A new flow for business users without a Betty Blocks account yet. They'll be able to request access to Academy and building tools through a form right inside Academy.
Timeframe: August '26