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
New features
Integrated Block Store search in Pages
Value: Enabling a seamless experience of finding and installing a block when searching in either widgets or components.
Impact: When searching for a widget or a component in Pages, you will now see results from the Block Store, which you can install and use without leaving the page builder.
Improvements & fixes
Bug fix: OnChange interaction box group
Value: We fixed the bug where the checkbox group component triggered the onChange interaction before the value was set. As a result, the filter interaction was basically always one change behind the actual. This is now fixed.
Impact: Users do not need to take any additional steps to benefit from this.
Bug fix: Property formatting
Value: We fixed the formatting of number properties in pages. When using the format 0.0, the runtime did not show the correct format, now it will show the correct formatting.
Impact: Users do not need to take any additional steps to benefit from this.
Bug fix: Autocomplete component label from model settings
Value: We fixed the bug that caused the autocomplete component to not inherit the label setting from the model settings.
Impact: Users do not need to take any additional steps to benefit from this.
Bug fix: OnActionDone on forms did not trigger when an error occurred
Value: We fixed the bug that the OnActionsDone toggle loading state interaction on a form wasn’t triggered when the form returned an error, so you needed to add another interaction (OnActionError) to make this use case work.
Impact:
- When creating a new form, users do not need to take any additional steps to benefit from this
- On existing forms, where an OnActionError interaction was used to toggle the loading state of a button, this can be deleted, as the OnActionDone is now working as expected
Up next
Update pages for quick navigation
Value: As a user, I can delete, duplicate and go to the runtime of a page from the quick navigation.
Impact: When opening the sidebar in Pages (quick-nav), you will see additional buttons when hovering over a page.
Timeframe: Within the next 2 weeks
New component tree release
Value: As a builder, I experience a faster and improved component tree when building pages.
Impact: When building pages I can open the tree view of my page which now has:
- Icons
- Search with jump-to
- Jump to a selected component
- Resizable toolbar
- Right-click open menu
- Zoom in/out in the component tree
- Better performance
- Show if a component has display logic applied
Timeframe: Within the next 2 weeks
Models
Up next
Slow query detector: enhanced DataAPI performance insights
Value: Builders now receive immediate, clear, and actionable warnings directly in their logs when the data API detects underperforming queries, specifically highlighting missing index issues. This allows for rapid identification and resolution of slow queries by adding necessary indexes. A more transparent and informative system empowers builders to proactively improve their app's performance, leading to a smoother and more efficient development experience.
Impact: Builders will be directly notified via warnings in their logs about slow data API queries caused by missing indexes, enabling them to optimize their data access patterns for better application scalability.
Timeframe: Q2 2025
Data compiler errors in the logs
Value: Providing builders with immediate, clear, and actionable error information regarding the data compiler within the logs will allow them to quickly identify and fix issues, minimizing downtime and maximizing their development efficiency. A more transparent and informative error-handling system will lead to a more positive and less frustrating development experience for builders.
Impact: No action is required nor expected from our users
Timeframe: Summer 2025
Actions
Up next
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 log 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.
Timeframe: Q2 2025
My Betty Blocks
New features
Merge change findability
Value: Enhance the merge overview to improve readability and navigation within the merger, improving the user experience.
Merge overview component options values
Value: All builders with merge permissions are able to see more structured value changes for component options to improve the readability of the merge overview, to validate changes before merging.
Impact: Users do not need to take any additional steps to benefit from this.
Improvements & fixes
Sandbox delete button not working
Value: As an organization user, I can delete the sandbox of an application by pressing the delete button of this sandbox in My Betty Blocks overview.
Impact: None, we have revised our code, and the delete button responds as intended, as opposed to not responding.
Up next
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.
Timeframe: expected mid-April
Enhance builder statistics and company dashboard
Value: As a company admin, I can view detailed application and builder information in My Betty Blocks company dashboard, allowing me to make data-driven decisions on application progression.
Impact: No changes will need to be made to enjoy this feature once it’s live.
Timeframe: We aim to release our latest updates by the end of April.
Master template functionality
Value: As a developer, I am able to create sub-applications from a master template, which governs the main features of my sub-applications. Maintaining an updated application structure for my sub-application while allowing me to make personalised changes to my sub-application.
We are currently researching the feasibility for the master deviation functionality, allowing a master template to push changes to a sub-application, and for the sub-application to accept these changes via a branch merging system.
Timeframe: We are in the early stages of developing the master templating feature, working towards providing smaller releases to provide you, our developers, with branching and merging updates as we update you on our progress.
Education
New features
Using the new logs overview
Learn how to log & debug your application, look into the performance of your actions and get a clear overview of successful and unsuccessful action runs in our new logs & action monitoring article.
Creating a mobile application using Betty Blocks and Cordova
Learn how to use the Cordova framework and Betty Blocks to create a mobile-first application, following this document.
How to use the Betty Blocks entity browser
Learn how to use the variables browser in your page builder called the entity browser.
Known application limits
To support builders in building optimised applications we have looked into building best practices and application limitations with the Betty Blocks services department to set up our known application limits article.
Improvements & fixes
Testing & debugging an action
Updated our testing & debugging article to reflect the new debug logging feature.
Textual and visual updates to educational content
- Application gallery - corrected sentence structure and visuals
- Filtering logic reference - updated to reflect filtering cases in all pillars of the platform
- Create a secure password reset function - refined sentence structure and added some best practices/tips
Up next
Low-code course in the Betty Blocks academy
Value: As platform trainee, I can learn how to use the Betty Blocks low-code content by following the academy low-code courses and tests.
Enable your low-coding skills by following the Betty Blocks low-code courses and learn how to expand your application using the various enablement toolkit functions provided by Betty Blocks.
Timeframe: the education team is currently researching the content and lesson goals for the low-code course and will continue with the creation of the Academy content once they are done.
Value: As a Betty Blocks platform trainee, I can test my skills via a Betty Blocks-supported test environment and get graded on level-based tests.
- Milestone 2: Certification and badging system
- Feature: Enhance user motivation and recognize achievements with certifications, tests, and badges.
- Value: Encourages user engagement through visible rewards, enhances credibility for users, and adds value to Betty Blocks’ platform.
We are working on the first version of testing and certification generation in our Academy environment and aim to deliver a test version in the upcoming sprint
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!