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

Release notes - April 2026.8

List of release notes from April 15, 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. Betty Genius: Filter collection variables on input fields
In Genius-generated Pages, we have introduced the ability to use input fields as dynamic filters for collection variables behind data tables and lists. Input components (such as search fields) are selectable within a collection variable’s filter configuration. When the input value changes at runtime, the filter is automatically applied and the updated data is queried. This enables a responsive filter experience. 

Limitations: Filtering will be triggered only on value change at runtime. Other events (e.g., on blur) are not supported yet. Applying multiple inputs together via a Button click is not yet available as well. 


2. Betty Genius: New components supported
In Genius-generated Pages, the following new components are available in the Genius-set: 

  • Drawer component – a panel that slides in from the edge of the screen (usually left or right) to show additional content without navigating away from the current page.
  • Snackbar component – a small, temporary notification that appears on the screen, usually at the bottom, to give users quick feedback about an action.
  • Collection component – a component to manage and render a list of items (records). Essentially, it’s a component that iterates over a data collection and outputs the UI components you dragged inside it for each item

3. Betty Genius: Dynamic boolean option type
In Genius-generated Pages, the Boolean option type has been enhanced. Instead of always setting a static True or False value, you are now able to set a direct property link. This direct property link results dynamically in a true or false. This unlocks many use cases like: 

  1. Set Button 'Loading' boolean option to true, if action is in loading state
  2. Set First name input 'Disabled' boolean option to true, if Last name has no value

Improvements & fixes

Several Pages compiler fixes

  • Redirect URL should only be used when logging in
    Fixed an issue where the new compiler incorrectly triggered redirect handling outside of authentication, causing unintended navigation behavior. Redirect URIs are now stored only when visiting a protected page without a valid access token.  

  • Handling of Data table on row click event
    Fixed a bug where on row click events on Data Tables were not triggered correctly in combination with the Filter interaction.
  • Handling of Image sub-properties
    Fixed a bug where using the URL or Name sub-properties of an Image caused a compile error when referenced on a page. These properties now work as expected without triggering compilation issues.

Genius component set improvement
Button Component  loading option
Button component in the Genius set now includes a new option for toggling a Loading state. In combination with the new direct property link option, “Is loading” from an action response variable can now be assigned to this setting. This means the button enters a loading state while the action is running and automatically returns to false when the action is complete.

Genius component set improvement
On backdrop click event on Dialogs and Drawers
Dialogs and drawers have received the on backdrop click event in the Genius component set. Typically used to close the component by clicking the (backdrop) overlay.

Page builder improvement
Improved UI of Boolean options
The UI in the options sidebar for boolean options has been updated. Instead of a checkbox input control, it now shows a button group with True and False options.



Up next

    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 pages that make up your application

    • Visualize which layouts are used on which pages

    • Visualize how pages and layouts are connected via navigational components, such as layout menu items or navigation buttons on pages

    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. 

    Timeframe: April '26


    2. Betty Genius: Filter collection variables 'on Blur' or 'on Button click'
    In Genius-generated Pages, you now have the ability to use input fields as dynamic filters for collection variables behind data tables and lists. Input components (such as search fields) are selectable within a collection variable’s filter configuration. In this feature, you will be to trigger the collection filtering not only on change of the input, but also on blur or on select events. As well as applying multiple inputs together via a Button click. 

    Timeframe: April '26


    3. Betty Genius: New components supported
    Genius-generated Pages will include the following new components:

    • Menu button component – a button component when clicked (or tapped) opens a list of options in a small dropdown. Typically used in menus or in data tables.
    • Tabs component – a component that lets you switch between different sections of content within the same view without navigating to a new page.

    Timeframe: April '26

    • Autocomplete component (with search) – a component that opens a dropdown with available options supported with an inline text search ultimately to select one option.
    • Multi autocomplete component (with search) – a component that allows you to select ‘multiple’ options including the inline text search.
    • Multi select component – a component that lets users choose multiple options from a list instead of just one. Often displayed as a dropdown with checkboxes, tags, or chips.

    Timeframe: May '26


    4. 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 manually 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. 

    Timeframe: April '26


    5. Betty Genius: Dialog enhancements
    In Genius-generated Pages, using dialogs will be enhanced with: 

    1. Set record context from a table to the variable used in a dialog
    2. On closing a dialog, reset the form object to its initial values

    Timeframe: April '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.
      • "" or NullIs empty
      • "Hello"Is not empty
    • Exists / Does not exist – Checks whether a Text field is defined (not null).
      • "" or "Hello"Exists
      • NullDoes not exist

    Timeframe: April '26


    7. Betty Genius: Automated Form action step syncing

    Previously, when you modified a generated form, the assigned rows in action steps (for example, in Create or Update Record steps) were not updated automatically. With this release, syncing is now automated. Whenever you change a Form (by adding, removing, or updating inputs), the assigned rows in the related action steps are synchronized with those changes.

    This enhancement makes managing form changes in Genius-generated Pages as seamless and user-friendly as in classic Pages, reducing manual updates and saving time.

    Timeframe: May '26


     

    Actions

     

    New features

    1. API key for the MCP server 

    Value: As your ecosystem of Model Context Protocol (MCP) servers grows, securing access becomes a top priority. This feature introduces a streamlined API Key authentication method, allowing builders to protect their MCP servers with secret tokens. It reduces security debt and ensures that only authorized clients can access your server’s resources and tools.

    Impact: Now you are be able to generate and manage unique API keys directly from your authentication profiles IDE. By authenticate your MCP server folder with an API key, all the actions in the MCP folder will inherit the API key authentication profile.


    2. Configurations in the actions of the MCP server

    Value: Users can now access application configurations (API keys, secrets, etc.) directly within the actions of an MCP server at runtime. This centralizes sensitive data management and removes the need for hard-coding. This allows the user to create DTAP MCP server api keys as well.

    Impact: Centralize all your sensitive data used in wasm actions again via the app configurations.


    Improvements & fixes

    1. Add variable to Array

    • Value: Users can add new items to existing collections to manage dynamic lists within their Wasm action.

    • Impact: Use this in any Wasm action by selecting a target array and the variable to add; this natively replaces manual "push" loops.

    2. Init array

    • Value: This provides a clean starting point for data collection by ensuring an array is properly instantiated and empty before use.

    • Impact: Found in the variable initialization menu, this should be used at the start of loops or processes to prevent data leakage from previous runs.

    3. Create object 

    • Value: Users can build structured data by pairing keys with values, ensuring output remains consistent with defined schema models.

    • Impact: Map your keys and values in the function configuration panel to generate a typed object.

    4. Parse JSON

    • Value: This converts raw string data into a navigable JSON object, allowing users to easily access nested properties from API responses.

    • Impact: Apply this to any stringified input via the function picker to transform "text" into "data" for use in subsequent logic steps.

    5. Stringify JSON

    • Value: Users can convert complex data objects into string format for storage or transmission to external systems and APIs.

    • Impact: Select any object or value within your workflow to generate a standard JSON string, simplifying the preparation of outbound HTTP request bodies.

    6. (Re)assign Variable

    • Value: This allows users to dynamically update the value of an existing variable to reflect new data or state changes throughout an action.

    • Impact: Replace the old variable with a new value in the Wasm action to ensure your downstream functions always reference the most current information.



    Contribution to Wasco.dev repository

    1. Glyphic API

    The Glyphic API Wasm component provides an interface for managing organizational call data, transcript snippets, and media. It streamlines secure authentication and data retrieval through optimized endpoints, enabling web applications to interact with Glyphic services.

    2. Open AI API

    This is a WebAssembly component that provides core OpenAI API integration functionality. It is designed to be composed with an HTTP proxy component that handles routing and HTTP protocol concerns.


    Up next

      Connect your own GitHub repository to WASM Actions

      Value: Developers can 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. It increases flexibility and makes it easier to scale and maintain complex logic.

      Impact: Users will be able to add a link of a GitHub repository to the list of repositories in the 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

      New features

      Streaming for faster AI responses

      Value: Solutioneer now streams AI responses progressively, so users see content appear immediately instead of waiting for a full answer.

      Impact:

      • Solutioneer feels significantly faster — users no longer face a blank wait before the AI responds.

      • Incremental rendering improves perceived performance, making AI-powered recommendations feel more responsive and natural.


      Improvements & fixes

      1. App importer improvements

      • Value: The app importer is now more robust and observable — table name length limits are enforced and activity is fully logged.

      • Impact: Previously, overly long table names could silently cause import failures. Both issues are now resolved, making app imports more reliable and easier to debug when something goes wrong.

      2. Text rendering fix for sandbox and branch names

      • Value: Characters like y, p, q, and j are no longer clipped in sandbox and branch name labels.

      • Impact: Names are now fully readable in the UI, removing a small but persistent display issue that affected visual polish across the platform.


      Up next

      Selectable suggestions

      Value: Users will be able to pick from AI-generated suggestions in Solutioneer, rather than having to describe their needs from scratch.

      Impact: This lowers the barrier to getting started. Users can quickly select a suggestion that fits their use case, reducing friction and improving the quality of results.

      Timeframe: April 2026


       

      Education

       

      New

      Model-based multilingual applications

      A practical guide to building multilingual apps where translations are mapped in the data model rather than in the builder. Because translations are stored as records, content editors can manage them directly in the application – adding, updating, or extending them at any time without changing the app structure. Includes a worked example with a multilingual FAQ and product catalog.


      Improvements & fixes

      Creating, updating, deleting, and assigning data (CRUD)

      Updated the CRUD article series – covering creating, updating, deleting, and assigning data. All five articles have been reviewed and refreshed with the latest guidance.

      Send email via SMTP step

      Updated the Send Email via SMTP article with a new use case on sending to multiple recipients, plus refreshed text and examples throughout.


       

      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!

      Platform roadmap