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
Number formatting
Value: We enhanced the number formatting feature to format billions numeric values properly in the page builder. When using the “0.00 a” formatting, every numeric value above the 9 digits receives the letter “b” when displayed. Some example data:
- 121230974 → “121.23 m”
- 3121230974 → “3.12 b”
Impact: Users do not need to take any additional steps to benefit from this.
Improvements & fixes
Improved Block Store search in Pages
Value: We’ve fixed an issue affecting the integrated Block Store search within Pages. Previously, if your search returned no matches from the default widget or component list, relevant results from the Block Store weren’t being shown either, even when they existed. This has been fixed now. Now, when you search within the page builder, you’ll get a complete set of results—including matching items from the Block Store—making it easier to find and use the widgets or components you need, even when the default list doesn’t have them.
Impact: Users do not need to take any additional steps to benefit from this.
Component tree resizing now persists correctly
Value: We’ve resolved an issue where the resized width of the component tree in the page builder wasn’t being saved properly. Although the width was supposed to persist by storing it in your browser’s local storage, a bug prevented this from working as expected. This has been fixed now. Now, when you resize the component tree, your preferred width will be accurately saved and automatically restored to the next page you will open in the page builder—just the way you left it.
Impact: Users do not need to take any additional steps to benefit from this.
Corrected drop position in component tree for nested elements
We’ve fixed a bug in the component tree where dropping a new component as the first child of a parent that already had children mistakenly placed it as a sibling instead. This has been fixed now. You can now accurately position components as the first child within a nested structure, ensuring better control over layout and hierarchy when building complex pages.
Impact: Users do not need to take any additional steps to benefit from this.
Decimal, Number and Price inputs exposed again to component-state
Value: We’ve updated the component-state feature to once again include the Number, Decimal, and Price input components. Due to recent changes, these inputs were unintentionally excluded from the "components" list (components shared in component-states) in the entity browser. This has been fixed now. You can now reliably use and share the values of Number, Decimal, and Price inputs across components via component states, just as expected.
Impact: This update will only be available in the latest version of the Number, Decimal and Price input components in the default Betty Block component set. Existing components already in use on pages that include this bug will not automatically receive this update.
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
Updated Pages overview, including the page last updated at information
Value: We will improve the Pages overview to make managing your content faster and more efficient. The update introduces a new “last updated” column, showing when each page was last modified and sorting capabilities on all columns, allowing you to quickly organize and locate the information you need.
Impact: You will be able to easily find the most recently edited pages and sort your data in the way that best fits your workflow, saving you time and improving navigation across your projects.
Timeframe: Q2 2025
Models
Improvement & fixes
AllowedKinds is extended with text-like types
Value: Users can now select rich text properties when configuring a text option or a value option with allowedKinds = ["STRING"].
Impact: Previously the allowedKinds was only a string variable, now you could also choose text-like types: date, datetime, email, password, rich text, string expression, multiline text and url.
This improvement will be released this week.
Up next
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
Improvements & fixes
Scheduled/logged actions overview
Value: Users will be able to see which actions are scheduled and which have logging enabled, directly from the main actions overview, without needing to open each action individually.
Impact: Users save time and gain quicker oversight of their actions, making it easier to manage actions efficiently.
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 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.
Timeframe: Within two weeks
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
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.
NL1 zone impact for company dashboard
Value: As a company admin, it is clear to me that applications running on NL1 are not considered towards the data displayed on the company dashboard
Impact: These values can be found back in the company dashboard and company applications table.
Applications zone is displayed in company applications table
Value: As a company admin, it is clear to me on what zone the applications within my company are running, so that I’m aware of things impacting these zones.
Impact: Navigate to the applications overview in the company overview, a new column has been added to the table.
Improvements & fixes
Building activity and active builders data
Value: All building activity & active builders data before 28 April is removed as it was incorrect.
Impact: These values can be found back in the company dashboard and the company applications table.
Non-developers counted towards active builders
Value: Some events that were triggered by non-developers caused incorrect metrics on the company dashboard.
Impact: These values can be found back in the company dashboard and the company applications table.
Application snapshots and versions clean-up
Value: When an application is removed, the associated snapshots and versions are cleaned up.
Impact: Improving the performance of merging.
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: Upcoming 2 weeks.
Education
New features
"Welcome to Academy" intro video
Added a new intro video for users first visiting the Academy.
Enabled certificate pages
A new certification flow has been introduced to the Academy. From now on, we enabled users to:
-
Generate the certificate for passing the final exam
- View the achievements on My Certificates overview page
Value: Encourages user engagement through visible rewards, enhances credibility for users, and adds value to Betty Blocks’ platform.
Essential path course assignments and quizzes
Practical assignments and quizzes for checking knowledge were added to the Essential path courses:
- Page design
- Models
- Page functionality
- Actions
Improvements & fixes
Auto-batched collections
Refined Processing large collections in actions, adding new info about auto-batched collections.
Up next
Enable certificate sharing functionality and improve UI for certification pages.
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
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
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!