Over the last two weeks, we have been working on improvements to the platform. This blog post provides a simple list of what has been changed and updated and what bugs have been fixed. You can read more about the release notes here.
Pages
Improvements & fixes
Improvement: Enhanced Pages overview
Value: The Pages overview has been upgraded to make finding and managing pages more intuitive and efficient. With smarter sorting, and better layout, navigating your pages in the overview just got easier.
What’s new?
- New column sorting - You can now sort every column in the Pages overview table. Organize your pages by name, path, or any other column — exactly how you prefer.
- New column ordering - We’ve restructured the column order and adjusted widths for better readability. The Name and Path columns now have extra space by default, helping you scan key info at a glance.
- Coming soon: A new last “updated at” column to the overview. Combined with sorting, this will make it easier than ever to find your most recently edited pages.
Impact: Users do not need to take any additional steps to benefit from this.
While implementing these enhancements, we directly applied the following two fixes:
- We fixed an issue where using the Public and Protected page filter tabs in combination with pagination in the overview caused unexpected behavior. When using the filter tabs, the pagination is always restored to page 1, ensuring a consistent and reliable filter experience.
- We fixed an issue where deleting the last page while using pagination in the overview could result in a blank screen. Now, if the last page is deleted, you’ll be automatically redirected to the first take of the pagination in the overview.
Fix: Double-click functionality in configuration wizard
Value: We’ve fixed an issue in the configuration wizard where double-clicking a property in the list failed to add it to the component when dropped onto a page. This behavior is now corrected—double-clicking a property will reliably add it as expected.
Impact: Users do not need to take any additional steps to benefit from this.
Fix: UI conflict between convert-to-partial modal and widget dropzones
Value: We resolved a z-index issue where widget dropzone borders would incorrectly appear above the convert-to-partial modal. Previously, this visual overlap could be distracting when creating a new partial. The modal now correctly displays above all dropzones, ensuring a smoother and clearer user experience.
Impact: Users do not need to take any additional steps to benefit from this.
Up next
Improved usability: Accessing logged-in user data on pages
Value: We will enhance usability when working with logged-in user data on pages by automatically providing authentication profile variables (representing logged-in users) across Pages. We are recognizing four key milestones:
- Enabling the use of authentication profile variables inside component options on a page.
- Allowing authentication profile variables to be used within filters of data components and other page variables on a page.
- Supporting authentication profile variables inside partials on a page.
- Enabling the use of current user role(s) in conditional display logic filtering on a page for easier configuration of show and hide logic based on the user’s role(s).
Impact: Users will no longer need to manually add data containers to make logged-in user information available across pages, simplifying workflows and improving efficiency without additional setup.
Timeframe: Q2 2025
Toggle form changes syncing per action step
Value: This feature allows developers to enable or disable form change synchronization for individual action steps that include a “value mapping” step option type, like the default Betty Blocks create and update steps.
Impact: This option enables the new time-saving synchronization feature to be applied to older forms. It allows you to synchronize form changes across multiple action steps simultaneously and provides the flexibility to disable the synchronization feature when it is not needed.
Timeframe: Q2 2025
Settings consistency
Value: Users will experience a more consistent platform by having settings structured similarly across different domains. In the page builder, page settings will be presented in the same way as action settings—via a right-hand side panel that opens when clicking the settings button in the top navigation.
Impact: Navigating and adjusting settings becomes more in line with the rest of the platform.
Timeframe: Q2 2025
Color component option overhaul
Value: Users will be able to choose colors more visually through a color picker instead of a textual dropdown, including the ability to select custom colors beyond your application theme values.
Impact: Users gain clearer visual indicators and greater flexibility when styling components, resulting in smoother, more enjoyable, and more precise customization of their applications.
Timeframe: Q2 2025
Page last updated at information in Pages overview
Value: In the Pages overview we will introduce a new “last updated” column, showing when each page was last modified with sorting capability.
Impact: You will be able to easily find the most recently edited pages—saving you time
Timeframe: Q2 2025
Actions
New feature
Hide values of input variables in Logs
Value: This functionality increases the control over sensitive data displayed in Logs by enabling the builder to decide which variable values will be shown on the Logs page and which will not. With it, improved security is implemented by preventing accidental exposure of confidential information like passwords and API keys.
Impact: This future improvement allows users to control the visibility of variable values in logs. Users can configure the visibility of each variable as desired.
Up next
Unlock high-code capabilities with the WasmBuilder
Value:
- Unlocking high-code flexibility within low-code: By enabling high-coders to visually model Wasm components, Betty Blocks can bridge the gap between the perceived limitations of low-code and the flexibility of high-code. This enables developers who desire more control and customisation within a low-code environment.
- Breaking vendor lock-in: The ability to export Betty Blocks actions as Wasm components provides customers with the significant value of application portability. This means their actions are no longer tied solely to the Betty Blocks platform and can potentially be run elsewhere, increasing customer freedom and reducing concerns about vendor lock-in.
- Expanding code language support: The feature's potential to transform code written in various languages (Rust, Python, etc.) into Wasm opens up the Betty Blocks platform to a wider range of development skills and project types, breaking the limitations of proprietary low-code technologies.
Impact: Transform code written in various languages into Wasm, which enables greater flexibility and more control over the application.
Timeframe: Beginning of Q3 2025
My Betty Blocks
New features
Application development activity status
Value: As a company manager, I want to manage inactive applications to improve organization and decision-making.
Impact: Our automated system will set an application to ‘Inactive' if it has the status ‘development’ but has had no building activity for 4 weeks. An inactive application will automatically be set to the development status if development continues. No other action needs to be taken.
Font updated to Fustat
Value: The font is updated to Fustat from Lato to reflect the same theming as the public website.
Impact: The default font within My Betty Blocks.
Improvements & fixes
Fix: Merge change type chips
Value: The merge overview now shows if items are of the type add, update or delete to see what the actual change was in the merge overview.
Impact: In the updated design of the merge overview this is displayed with the chips.
Fix: Linking to items from the merge overview
Value: Navigating via certain items resulted in an infinite loop in the building environment.
Impact: Selecting the text of items in the merge overview links to the building environment of these items to validate the changes made.
Fix: Action event path update in merge overview
Value: Updates to an action event path should be displayed in the merge overview so that these changes can be merged.
Impact: No action needs to be taken.
Improvement: Sorting and filtering of application zone in application overview
Value: Applications are easier to find based on their application zone within the application overview.
Impact: Use the new zone filter dropdown above the table for filtering. To sort the table click on the header of the table that says zone.
Up next
Resolve already modified merge conflict
Value: As a user with merge change permissions, I’m able to choose the incoming or current changes in the merge overview, so that I can merge the desired changes to my application
Impact: This functionality is available for our branching and master template functionality. These are both behind a feature flag to be able to be adopted
Timeframe: Within 4 weeks
Education
New articles
The article details the process for manually configuring permissions for remote models.
Create a Next-gen mutation logging feature
An article detailing how to develop a mutation logging feature that helps track which records have been created, updated, or deleted.
Improvements & fixes
Code blocks in Classic docs
Improved look and usability of code blocks in Classic documentation.
Pages standards & best practices
Updated article on best practices for using the page builder: eliminated outdated features, incorporated new functionalities, and refreshed images.
Updated the article to reflect the latest UI enhancements in Pages.
Up next
Create new assignments and quizzes for the Advanced path.
Timeframe: within 4 weeks
Later this year:
- Milestone 3: Customer and management portals
- Feature: Enable tailored learning experiences for different user roles and provide administrators with insights
- Value: Supports scalability by offering role-based learning, empowers administrators with actionable insights and enhances user experience
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!