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

Release notes - August 2026.17

List of release notes from August 18, 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: Genius Chat replaces Modules for multi-page generation
Betty Genius AI is getting a major upgrade, rolling out in three releases as capabilities move from the current experience into the new Genius AI experience. This release delivers the first step: multi-page generation has moved from Modules into Genius Chat, and is now available to use. AI page editing and single-page generation will follow in upcoming releases.

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 — Modules overview and "create new module" flow are phased out and replaced by the Genius Chat session overview, where you start and manage sessions instead.
  • Multi-page generation, now in chat — multi-page generation has moved from "new module" into 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, keep chatting — you can iterate on it conversationally until it fits.
  • A new page generation engine under the hood — page generation now runs on a new setup and architecture, delivering fewer functional loose ends, fewer generation errors, faster generation times, and a future-proof foundation for upcoming features.

2. Betty Genius: translating Select static options
In Genius-generated Pages, Select, Radio, and Autocomplete inputs are now 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.

3. Betty Genius: populate model list property options for Data Table filtering
In Genius-generated Pages, you are now 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.

 

Improvements & fixes

Betty Genius component set:
1. More default value options for Price and Text Area inputs
Price inputs can now default to a decimal property type present in an Action Response variable, and Text Area inputs can default to a single-line text property also present in an Action Response value. This allows Builders to pre-fill forms with the result of a previous action without extra workarounds.

2. Collection component can now be nested inside a List component manually
The Page Builder previously blocked manually placing a Collection component inside a List component, even though Genius AI could generate that exact structure. This allows Builders to recreate by hand any structure that Genius AI generates as well.

Pages compile validation:
1. Clearer error state when an order-by property is deleted
If a property used in an object variable's order-by setting was deleted, the page failed to compile with no visible error, and the page variable modal's delete button could get stuck disabled. Builders now see a clear "property not found" error pointing at the exact problem.


2. Fixed sidebar not opening after navigating from a compile error
Clicking a compile error to jump to a page-level interaction left the sidebar locked, so clicking any component afterward failed to open its properties panel. This is fixed now.

Pages compiler:
1. Data query error at runtime
The new Pages compiler wasn't handling properties correctly where the database names containing an underscore followed by a number (e.g. is_2fa) which caused the entire runtime data query to fail. This issue has been fixed now. 

2. Fixed collection filtering crashes at runtime
Several scenarios involving collection filters could crash a page at runtime: filtering an Autocomplete on a filtered collection, using a Text page variable in a nested Collection's filter, and sending an empty filter condition. Filtered and nested collections now behave reliably instead of crashing.

3. Fixed stale default value after edit-detail-edit navigation
Navigating from an Edit page to a Detail page and back to the Edit page again, showed the previous value instead of the value the user just changed. This is fixed now. Builders and end users see the value they actually saved, which fixes a data-integrity concern.

Page builder:
1. Fixed entity browser search in form and response objects
Searching within the Form or ActionResponse objects always returned "No matching search results," and clearing the search didn't restore the full list. Builders can now search through these schemas of the objects, the same way they can everywhere else in the entity browser.

2. Fixed contentEditable text fields rejecting spaces
The VARIABLE component option type in the IDE didn't accept the space character. This has been fixed now. Builders can type normal text without the field silently dropping spaces again.

 

Up next

1. Betty Genius: AI page editing to Genius Chat
Betty Genius AI is getting a major upgrade, rolling out in three releases as capabilities move from the current experience into the new Genius AI experience. This 2nd release focuses entirely on: enabling the AI page-editing capability via Genius chat sessions. 

What's included in this release?

  • Sidebar prompt box removed: The page-edit prompt box in the Page Builder's left sidebar is being phased out and consolidated into Genius Chat sessions.
  • New chat mode: Genius Chat introduces a new "Think · Plan · Preview" mode.
  • Live preview on canvas: In Preview mode, page changes made via Genius Chat appear directly on the canvas — you can accept or reject them before they're applied.
  • Smarter context awareness: Genius Chat now recognizes whether you're editing a page, action, model, etc. This improves the UX and gives Genius AI higher-quality context, leading to better results.

Timeframe: September '26

2. Betty Genius: Single-page generation to Genius Chat
Betty Genius AI is getting a major upgrade, rolling out in three releases as capabilities move from the current experience into the new Genius AI experience. This 3rd and last release of the transition focuses entirely on step 3: enabling single-page generation via Genius chat sessions.

What's included in this release?

  • Single-page creation moves to chat: The "Create single-page" prompt will now connect directly to Genius Chat — starting a new prompt for a new page kicks off a new session.
  • Image upload support: Use a screenshot or design mockup as input to generate your page.
  • Generic file upload in chat: Beyond images, you can now upload files like text or CSV documents — for example, requirements docs or process flows — to kick off a proposal generation in a Chat session.

Timeframe: September '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: new 'Set Values' interaction capabilities
    In Genius-generated Pages, we will enhance the Set Values interaction function: 

    • Use action response variables as values in Set Values
      The Set Values interaction (page-level and component-level) will allow an action response property to be selected as the value being assigned, not just as a target. This allows builders to pipe an action's output (e.g. a calculated date) straight into a page variable for example. This removes the current restriction that blocks selecting action response properties as Set Values values.
    • Use Form schema properties as the target variable in Set Values (Up next)
      The Set Values interaction will allow a Form schema (custom object) property to be selected as the variable being set, on both page-level and component-level interactions. This allows builders to assign values — for example from an action response like an address lookup — directly into individual Form schema properties (e.g. City, Street). It removes the current restriction that blocks selecting Form schema properties as a Set Values target.

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

    Up next

    1. AI-generated Wasm Actions

    • Value: Users can generate actions automatically using Genius based on prompts. This reduces manual configuration work and helps teams build automations faster with fewer setup errors. AI-generated actions also make it easier for non-technical users to create consistent business logic and accelerate application delivery.
    • Impact: After release, users will be able to access AI-generated actions directly from the Genius chat when creating or editing an action flow. Users can describe the intended outcome in natural language, after which AI will suggest and configure the required actions automatically. Existing manually configured actions will continue to work as expected and can be further optimized using AI-generated suggestions.
    • Timeframe: End of August.

    2. OAuth for MCP servers

    • Value: Lets MCP clients authenticate against your app using its existing login methods (username/password, FusionAuth) instead of a separate MCP-specific login flow.
    • Impact: Will apply to any application exposing an MCP server; no action needed from builders once released.
    • Timeframe: Within the upcoming 4 weeks.

     

    My Betty Blocks

     

    New features

    1. Software catalog public release

    Value: Company admins are now able to create an overview of all the software they use within their company and their available connections, so that the software you already have is clear before a new app is started, saving time and budget.

    Impact: The software catalog can be found in the company overview, for more info read the following blog post: https://blog.bettyblocks.com/introducing-software-catalog

    2. Import features with your software catalog

    Value: You can now import the features of your software along with the software itself, so you no longer have to add them by hand afterwards.

    Impact:

    • Features are included in the downloadable example import template.
    • A single import brings in both your software and its features.
    • Imported features land in the right structure. They show as collapsible sections in view mode and as Markdown in edit mode.
    • Large catalogs can be onboarded in one go instead of item by item.

    3. The Solutioneer suggests existing apps before you build a new one

    Value: During ideation, the Solutioneer now checks your catalog and suggests apps that already solve your problem, so you avoid building a duplicate.

    Impact:

    • Suggestions appear in the chat once ideation reaches 60% progress.
    • Each suggestion shows the title, a short summary of purpose and functionality, and a match percentage.
    • Suggestions move to the sidebar after a refresh or on a later visit, so they stay available.
    • Teams reuse what they already have instead of duplicating effort.

    Disclaimer: Solutioneer is behind a feature flag, reach out to support if you want to try it.

     

    Improvements & fixes

    1. More reliable application creation

    • Value: Applications that used to appear stuck or failed during creation now finish properly.

    • Impact: Creation jobs are no longer interrupted when the underlying service restarts. A check runs every five minutes to catch applications stuck without a running job and marks them clearly instead of leaving them hanging.

    2. Searchable dropdowns accept input again

    • Value: You can search and filter inside dropdowns in modals again, instead of scrolling through the full list.

    • Impact: Search fields in pickers such as Install Block, Create application, and Create organisation now accept keyboard input and filter properly. Clicking the cross clears the input. This unblocks anyone working in a company with a long list of organisations or applications.

    3. Application status and type changes work in every language

    • Value: Changing an application's status or type now works regardless of your interface language.

    • Impact: The dropdowns sent the translated label to the backend instead of the underlying value, so changes were rejected in Dutch and other non-English interfaces. Some options happened to match the English value and still worked, which made the problem look random. Both dropdowns now send the correct value every time.

    4. Domain view shows pages and webblocks hostnames

    • Value: After adding a hostname, you can now see whether it points to pages or webblocks.

    • Impact: The domain view returned an empty result for the pages and webblocks hostnames, leaving you unsure whether the hostname had been added at all. Both now display correctly.

    5. Invitation links for non-builder users

    • Value: People invited as a user, rather than a builder, now land in the right place when they accept an invitation.

    • Impact: The invitation email sent every user to the IDE. Users without builder permissions got caught in a redirect loop and could not get in. Users are now taken to the runtime, while builders still go to the IDE.

    6. Passwords with special characters

    • Value: Passwords that the interface marks as valid are now actually accepted.

    • Impact: The frontend and the backend used different lists of allowed symbols, so some valid-looking passwords were rejected with a vague error. The two now match, which removes a confusing dead end during sign-up and password resets.

    7. On-premise imports with ActionJS actions

    • Value: On-premise customers can import applications that use ActionJS actions again.

    • Impact: Importing no longer skipped the default storage bucket that ActionJS actions depend on, which left actions unable to run after import. Delivered as a hotfix to unblock a customer release.

    8. Security and dependency updates

    • Value: The platform runs on patched, up-to-date components.

    • Impact: We resolved a high-severity PostCSS advisory, upgraded styled-components, refreshed the Erlang, Elixir, and Alpine versions behind the assets API, and updated the platform service dependencies. These changes are invisible in daily use, but they keep known vulnerabilities out of the platform and clear the path for future framework upgrades.

     

    Up next

    1. System events in the audit log

    • Value: You will be able to see which automated system events affected your customer, not just what people did.

    • Impact: Automated changes, such as an application being set to inactive, will appear in the audit log and be marked as system events. You will be able to filter on them, which closes a gap in your governance trail.

    • Timeframe: August 2026

    2. Notifications when an application goes inactive

    • Value: Application and organisation admins will be told by email when an application is set to inactive, so nothing goes quiet without warning.

    • Impact: The email will explain why the application became inactive, link straight to it, and say what happens next if no action is taken. Notifications are deduplicated, so nobody gets spammed. Existing inactive applications will be included.

    • Timeframe: August 2026

    3. Full details for suggested existing apps

    • Value: When the Solutioneer suggests an existing app, you will be able to open it and see exactly what it does before deciding.

    • Impact: A drawer will show the full description, all features, and why the app was matched to your request. From there you can close it, decline and continue building something new, or adopt the app. Adopting a custom or external app opens a request to its owner; adopting a Betty Blocks application takes you straight there if you have access.

    • Timeframe: September 2026

    Important: Solutioneer is behind a feature flag – reach out to Support if you want to try it out.

    4. Archived application status

    • Value: You will be able to manage applications you no longer use, keeping your overview clean and your decisions clear.

    • Impact: Archiving a production application will also archive its sandboxes and branches, and applications left inactive will move to archived automatically after a set period. Statuses will be visible in the company applications overview and editable in the application detail view, with every automatic change recorded in the audit trail. The automatic behaviour is off by default per customer, so nothing changes without you enabling it.

    • Timeframe: September 2026

     

    Education

     

    New

    Building Entra ID SSO
    A step-by-step guide to the Betty Blocks side of the Entra ID OIDC SSO integration, covering the setup in the builder.

    Improvements & fixes

    FAQ: Security & governance
    Updated overview of our security measures: access control and authentication, data security (including AI data security), backup and recovery practices, and more.

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