Skip to content
Classic documentation
  • There are no suggestions because the search field is empty.

Release notes - August 2026.16

List of release notes from August 4, 2026


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: Set language for multilingual Genius-pages
In Genius-generated Pages, the Set language interaction has been added and is now available to use on your page. This allows to drive language switching from a query parameter, a language selector, the logged-in user's preferred language, or a page variable, then have the change apply immediately with the correct <html lang> and translated content keys defined in the Translations overview.  The Set language interaction can be either trigger at page or component level, to change the application's active language. 

 

Improvements & fixes

Pages compiler bug fixes
1. Conditional components evaluate correctly again
Fixed cases where conditional components, including nested conditionals, didn't apply their conditions correctly, which had caused broken pages in some applications.

  • Value: Conditional logic on components now renders as configured, including when conditions are nested inside each other.

  • Impact: Prevents pages from silently showing the wrong content when conditions are combined.

2. Session expiry no longer shows an incorrect access-denied page
Fixed an issue where an unexpected "Access denied" error page appeared at runtime when a user's session had expired.

  • Value: Users with an expired session now see the correct, expected behavior instead of a confusing access-denied error.

  • Impact: Reduces support tickets caused by misleading error messaging on session timeout.

Betty Genius bug fixes:
1. Page duplication no longer breaks variable and filter references
Duplicating a page could leave several interactions in a broken state: Refetch page variable, Autocomplete filters, Set values, and Run action mappings could all lose their variable references after a copy.

  • Value: Copying a page is now reliable — its interactions keep working without needing to be reconfigured by hand.

  • Impact: Reduces rework and confusing error states for anyone using page duplication as a starting point for new pages.

2. 'Run action' interaction mapping fixes
Fixed issues where mapping a Checkbox action input, or mapping a page input variable to an action input variable, could produce an incorrect mapping or a compile error.

  • Value: Run action interactions map their inputs correctly regardless of variable type.

  • Impact: Removes a class of compile errors that blocked publishing pages using these mappings.

3. Unauthenticated users now land on the login page
Fixed an issue where unauthenticated users were redirected to a broken URL instead of the login page on the authentication profile (in case this was a Genius page).

  • Value: Users who aren't logged in are sent to the correct login page every time.

  • Impact: Removes a dead-end redirect that could confuse or block users trying to sign in.

4. Action error messages display correctly in text
Fixed an issue where an error message property from a page action response variable rendered as raw object output when combined with other text in a Text component.

  • Value: Error messages shown to end users are now readable instead of showing raw object output.

  • Impact: Improves the clarity of error feedback surfaced on running pages.

5. Collection Total count of zero now display in Text components
Fixed a bug where a collection variable total count of zero didn't display at all in a Text component at runtime.

  • Value: Text components now correctly show a value of zero instead of appearing blank.

  • Impact: Prevents pages from silently hiding meaningful data when a count or total is zero.

6. Clearerar error messages from the Raise Error action step
Fixed the error message produced by the Raise Error step in a Wasm action, which wasn't displaying as expected.

  • Value: Custom error messages raised from actions now show up the way builders configured them.

  • Impact: Makes it easier to surface and debug meaningful error messages from actions.


7. Fixed a compile error with reserved-sounding iterator names
Using certain words as the name of a collection iterator variable (such as "Case") caused a compile error. This has been mitigated.

  • Value: Builders can name collection iterators freely without breaking the compile.

  • Impact: Removes a naming-related compile error that wasn't obvious to diagnose.

MUI component set bug fix
Data Table filtering with multiple Autocomplete fields
Fixed a bug where filtering a MUI Data Table component (by the Filter interaction) with more than one Autocomplete component applied OR logic instead of combining filters with AND logic.

  • Value: Using compound filter interactions on a Data Table now narrows the Data Table results as expected.

  • Impact: Restores correct filtering behavior when several filter inputs on one table.

 

Up next

1. Betty Genius: Genius Chat replaces Modules for multi-page generation
Betty Genius AI is getting a major upgrade. We're rolling out the new Genius AI experience in three releases, each moving a capability from the current version into the new Genius AI version in the platform:

  1. Multi-page generation — from Modules to Genius Chat
  2. AI page editing — to Genius Chat
  3. Single-page generation — to Genius Chat

This first release focuses entirely on step 1: moving multi-page generation out of Modules and into the new Genius AI experience via Genius Chat. Modules and the modules overview will be phased out in favor of Genius Chat. 

What's included in this release?

  • Genius AI centralized chat
    A single, app-wide chat to manage all your Genius AI sessions whether you're building something new, refining what already exists, or thinking out loud with Genius AI as your expert co-worker.

  • A new home for sessions
    The Modules overview and "create new module" flow are phase out and replaced by the Genius Chat session overview, where you can start and manage new sessions instead.

  • Multi-page generation, now in chat
    Multi-page generation moves from "new module" into new Genius AI chat sessions.

  • From prompt to proposal
    Genius AI turns your prompt into a structured proposal — with clear functional requirements for each page, layout, and action. If the proposal isn't quite right yet, just keep chatting: you can iterate on it conversationally until it fits.
  • A new pages generation engine under the hood

    Page generation itself runs on a new setup and architecture, designed to deliver:

    • Fewer functional loose ends in generated pages
    • Fewer generation errors
    • Faster generation times
    • A future-proof foundation for upcoming features (future-readiness)

Timeframe: August '26

2. Betty Genius: translating Select static options
In Genius-generated Pages, Select, Radio, and Autocomplete inputs will be able to use translation keys for their static options, so the display label shown to end users can be translated for multilingual purposes. This allows builders to mix translation keys within static options and removes the need for workarounds to build this use case. 

Timeframe: August '26

3. Betty Genius: set page language for accessibility
In Genius-generated Pages, you will be able to set the HTML language attribute on your pages instead of it always being fixed to English. A new "Default page language" setting in your application settings sets the language for the whole app, and a "Page language" field on individual pages lets you override it per page. This allows screen readers and other assistive technology to announce content in the correct language, helping you meet accessibility legislation requirements.

    Timeframe: August '26

    4. Betty Genius: populate model list property options for Data Table filtering
    In Genius-generated Pages, you will be able to configure Select, Radio, and Autocomplete inputs with a List property for options setting, letting their options be populated directly from a model's List property instead of manually re-entered as static values. This allows you to wire a Select input straight to a List property (e.g. Invoice.Status) and use it to filter a bound data table, without duplicating the property's values as static options.

    Timeframe: August '26

    5. Betty Genius: catch invalid component interaction metadata
    In Genius-generated Pages, the compilation flow will include the metadata validation of component-level interactions, to catch missing references such as page variables, components, or actions. This prevents pages from being compiled with broken interaction references. Builders get a clear error state directly on the affected interaction (e.g. "Page variable not found"), plus a matching entry in the error overview that deep-links straight to the broken interaction, so issues are caught and fixed at compile time instead of surfacing as runtime failures for example. 

    This increment will only affect Genius-pages, and will not be compatible for pages generated with the MUI component set. 

    Timeframe: August '26

    6. 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.

    Timeframe: August '26

    7. 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: August '26

    8. 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.
      • "" or Null → Is empty
      • "Hello" → Is not empty
    • Exists / Does not exist – Checks whether a Text field is defined (not null).
      • "" or "Hello" → Exists
      • Null → Does not exist

    Timeframe: August '26

    9. 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

    10. Betty Genius: new Genius components supported
    Genius-generated Pages will include the following new components in the Genius set

    • 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: September '26

     

    Actions

     

    Bug fixes

    • Recurring Actions compiler crash on Wasm steps: Fixed a compiler state issue that caused a generic api_error on previously-working Wasm steps, forcing builders to delete and re-add steps as a workaround.

    • Wasm action logs didn't show errors Wasm action logs now display the error state and the actual error message when a step fails, instead of looking like the action ran fine.

    • Compile error when a schema property was missing Actions using a removed schema-model property now fail with a proper compile warning instead of crashing or silently returning null. 

    • Compiler error on Create, Update, and Expression steps Fixed a Wasm package-merge error that broke compilation whenever a Create Record, Update Record, or Expression step was added to the canvas.

    • MCP/Wasm actions became unavailable after a while Fixed a "No backend available" error that made Wasm actions and MCP server actions unresponsive after running for some time, previously only fixable with a manual recompile. 

    Up next

    1. Compile NextGen Actions to Wasm

    Builders will be able to switch a single action from a Next Gen Action to the new Wasm runtime, without rebuilding it from scratch.

    • Value: With the ability to compile NextGen actions to Wasm, gives the users the opportunity to download their backend to run it elsewhere. 
    • Impact: Options tab of an action's settings — toggle "Compile to Wasm" on or off.
    • Timeframe: Half of August

    2. OAuth support for MCP servers

    • Value: MCP clients will be able to authenticate against a Betty Blocks app using its existing login methods (username/password, FusionAuth) instead of a separate auth flow.
    • Impact: Data-api becomes an OAuth 2.1 Authorization Server, exposing standard /oauth/authorize and /oauth/token endpoints while existing runtime APIs keep working unchanged.
    • Timeframe: End of August

     

    My Betty Blocks

     

    New features

    1. Create a new app straight from Solutioneer

    Value: After finishing a Solutioneer conversation, you can now turn the outcome into a new application in one click.

    Impact:

    • "Gather requirements and build" opens the create application modal, with the name, initials and identifier pre-filled from your Solutioneer input.
    • The Solutioneer outcome is stored with the new app, so it can be used as a starting point for building in the IDE.
    • Template selection is skipped, making the path from idea to app shorter.

     

    Disclaimer: Solutioneer is still behind a feature flag. Request feature flag via this email: anton.vandenberg@bettyblocks.com

    2. Import your existing software catalog

    Value: Company admins can now populate the software catalog in one go by importing an existing portfolio.

    Impact:

    • Upload a CSV or XLSX file and rows are mapped to catalog entries with name, description, URL and owner.
    • Known public software is added to your portfolio without creating duplicates; unknown items are added as custom software.
    • An import summary shows what was added, skipped or failed.

    3. Edit software icons in the catalog

    Value: Customer admins can now change the icon of a software item in the software catalog.

    Impact:

    • Icons can be edited directly when edit mode is enabled.
    • Keeps your catalog recognizable and up to date.

    Disclaimer: Software catalog is still behind a feature flag. Request feature flag via this email: anton.vandenberg@bettyblocks.com

    Improvements & fixes

    1. Prompt assistant keeps your added scope

    • Value: Specifications you add to the build plan during onboarding are now stored correctly.

    • Impact: Added scope no longer disappears from the functionality list within the trial flow. It is included in the final generated prompt, so your app matches what you asked for.

    2. Asset links restored

    • Value: Application assets that returned a 404 after a storage migration are reachable again.

    • Impact: Asset URLs resolve correctly, so files referenced by your applications load as expected.

    Up next

    1. View existing apps in Solutioneer

    • Value: See what an existing app does before deciding to reuse or adapt it.

    • Impact: A detail view will show the app's features, description and owner, plus why the AI suggested it as a match.

    • Timeframe: August 2026

    2. Notifications for inactive apps

    • Value: Admins get an email when an application is set to inactive.

    • Impact: The email explains why the app became inactive, links straight to it, and warns about the next step (archiving), so unintentional deactivations can be fixed in time.

    • Timeframe: August 2026

    3. Archived application status

    • Value: Inactive applications will automatically move to an archived state, keeping your environment clean.

    • Impact: Statuses are visible in the company overview and application detail view, and every automatic change is logged in the audit trail.

    • Timeframe: August 2026

     

    Education

     

    New

    Variables in Actions

    A guide to the four categories of variables in actions: input, action, step and output variables. Each category covers its available kinds, use cases, and examples.

    Updated

    Interactions in Genius

    Two interactions added: Login and Logout, both with usage examples. Redirect also got more options. Under Redirect to, pick the destination type: an internal page in the app, or an external page via URL. The URL can be typed in or pulled from a variable, such as an action's response.

    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: Mid August '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