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.
Due to an update from our documentation provider, docs may appear different than what they usually look like. We are working on solving this as soon as possible.
Pages
Improvements & fixes
Clear 'Selected record'
Value: The clear interaction has been enhanced to support a new use case—clearing the ‘selected record’ component-state attributes of data tables and data lists. Previously, this interaction was only available for input components, allowing users to clear their values. With this update, data tables and data lists can now also be selected as a ‘target component’ for the clear interaction. This feature is especially useful when working with multiple tables or lists to filter a single page variable. At runtime, applying the clear interaction to a data table, for example, will only clear the value stored in its ‘selected record’ attribute, without affecting any of the data records loaded by the component.
Impact: This update will only be available in the latest version of the data table and data list components in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
Bug fixes: New price and decimal inputs
Value: In a recent release, we introduced new price and decimal input components for greater ease of use. After receiving valuable feedback from early adopters, we addressed their concerns in this update. These fixes enhance the stability and reliability of price and decimal inputs. Below is a list of the resolved issues:
- Clear issue: Values cleared using the ‘clear’ interaction would reappear when hovering over the input.
- Reset issue: Similarly, values reset using the ‘reset’ interaction would reappear on hover.
- Visibility after pasting: Pasted values inside the inputs were only visible after clicking outside the input field.
- Console errors: Excessive console errors were generated while editing the inputs at runtime.
- Min/max validation mismatch: Default min and max validation values did not align with backend database validations. The min/max options now receive default values to ensure consistency.
- Invalid negative values: When the min validation was set to `-1000000000`, submitting `-123.456.789,99` was incorrectly flagged as invalid. This has now been fixed.
Impact: This update will only be available in the latest version of the price and decimal inputs in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
Bug fix: Removing rich text input and syncing
Value: Action syncing ensures that form changes automatically update form action steps, streamlining the process of building business logic. However, when a rich text input component was removed from a form, the synchronization did not update correctly—the action steps still expected the removed component. This issue has now been resolved, ensuring proper synchronization and consistency.
Impact: Users do not need to take any additional steps to benefit from this. This fix is automatically applied to all new form action synchronization.
Bug fix: Default label property for checkbox group
Value: When using checkbox group inputs on a page, a label value is used to render all options. By default, this label is inherited from the model or relational model. Previously, this inheritance only worked correctly if the label property had been manually updated in the model. Otherwise, no label was returned unless it was changed or explicitly set using the ‘Label for options’ option—a feature meant for overriding, not as a default. This issue has now been fixed, ensuring that checkbox group inputs consistently inherit the correct label property by default, improving reliability and ease of use.
Impact: This update will only be available in the latest version of the checkbox group input in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
Bug fix: Filter component and date-time input
Value: When using the filter component with a date-time property, the selected date and time were not displayed correctly—only the date appeared in the input. This issue has now been fixed, ensuring that both the date and time are displayed properly.
Impact: This update will only be available in the latest version of the filter component in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
Bug fix: Formatted default values in inputs
Value: The ‘value’ option in input components has been updated to resolve an issue where formatting was incorrectly applied to selected properties. Previously, when a property was chosen for this option, the platform automatically applied formatting to its value. However, default values in input components should always use the unformatted values from the database. Formatting should only be applied by the input component itself, based on the developer’s configuration. This fix ensures that default values remain unformatted, allowing inputs to render values correctly and handle formatting as intended.
Impact: This update will only be available in the latest version of any input component in the default Betty Block component set. Existing components already in use on pages will not automatically receive this update.
Up next
Toggle form changes syncing per action step
Value: This feature allows developers to enable or disable form change synchronization for individual action steps that includes 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: Q1 2025
New “add form input” option on form components
Value: We’ll introduce a new feature that simplifies the process of adding form input components directly to forms. Instead of using the drag-and-drop method from the sidebar, users can now click the "add form input" option within a form component. This launches a guided wizard to streamline the process of adding new inputs. This update will make it easier to enrich forms with new input components, even in scenarios with restricted page wrapper access.
Impact: The impact of this feature are twofold:
- Simplified form editing: Form editing will be easier for less advanced users who are less experienced with drag-and-drop functionality. This enhancement reduces the effort required to customize forms.
- Ability to change forms from a locked page wrapper: This feature can be applied to page wrappers, allowing developers to modify forms embedded within locked page wrappers. For example, forms used in the backoffice page template will be updated without needing to unlock the page wrapper, providing greater flexibility and convenience.
Timeframe: Q1 2025
Models
New features
Replacing the current cloud storage
Value: We are currently replacing our current cloud storage provider with Wasabi Technologies as our subprocessor for cloud storage. This change is part of our continuous efforts to optimize our services and ensure we leverage the most efficient and secure solutions available.
Impact: No action is required nor expected from our users. This transition will be seamless, and we are doing everything to minimize the impact on our services and are expecting no downtime during the migration.
Timeframe: Customers will be notified when the migration of their applications is scheduled.
Actions
Improvements & fixes
Send warning when configuration is not found
Value: previously, when you would use a configuration in one of your action steps, then delete the configuration, the compiler wouldn't send a warning for missing configuration. This has now been resolved, and the compiler will send a message preventing you from running into an error.
Up next
Enhanced debug logging experience
Value: (Debug)logging of an action is currently a very time-consuming effort. To check where an action fails to execute or if information about the execution is needed, the builder currently needs multiple log steps after every action step to check the action flow. By enabling logging the whole action at once and optimizing the logs page to display the information of the action execution, we enable the builders to debug their action within minutes instead of hours.
For the last two weeks, we have been rolling out a series of updates to enhance the debug logging experience.This all is available behind a feature flag that can be requested via Support.
What you will unlock with this feature flag:
- Turn logging on/off
- Feature: Toggle to enable or disable logging for each action, available in the action settings.
- Value: Provides control over logging, allowing builders to enable it only when needed to reduce clutter and focus on critical information.
- Log page optimization
- Feature: Expand/collapse logs by action step for easier navigation and links to specific actions/steps directly from the log page for quick access.
- Value: Improves readability and accessibility, making it easier to pinpoint and resolve issues.
- Variables on log page
- Feature: After this milestone, the variables and its values will be printed on the logs page for every action step.
- Value: Improves the debug experience, making it easier to pinpoint and resolve issues.
- Feature: Search and filter logs by timestamp and type and sort columns, with the default sort set to date and time (latest log first).
- Value: Allow builders to quickly locate relevant logs, reducing time spent searching for specific events.Advanced filtering options
Timeframe: The public release of the improved debug logging experience is planned for mid March.
Query splitting
Value: Improve your application's ability to manage functionalities that use complex filtering without compromising performance, by improving the query-splitting on permission filters. This will optimize query performance and ensure users can efficiently retrieve data they are authorized to access.
Impact: For optimal use, ensure data security by strictly adhering to permission-based access control.
Expected timeframe: Early March
My Betty Blocks
Up next
End-user activity tracking
Value: Company admins are able to view and monitor the active end-users within their company and per application within the company, so that they can govern the value of the applications.
Impact: On the company overview dashboard a new graph is available that shows the total number of active end-users. On the company overview applications table a new column is added that shows the total number of active end-users per application.
Timeframe: Upcoming 4 weeks.
Company growth metrics
Value: Company admins are able to see the company statistics updates over time allowing them to govern the value of the company account and its applications.
Impact: The company overview dashboard now shows the statistics in a graph including the growth number for the selected period. In the applications table of the company overview the growth numbers are displayed in the columns for the selected period per application.
Timeframe: Upcoming 4 weeks.
Company storage usage
Value: Display the total storage usage of an account and application basis without temporary storage being included so that a realistic view of actual storage usage is displayed.
Impact: The storage will be displayed on the company dashboard and applications table.
Timeframe: Upcoming 4 weeks.
Education
New
The SDLC-flow application template
Do you want to learn how to follow the ideal flow for application development? An application template has been created that allows you to create your own initiatives and follow a checklist to ensure your development team follows the best practice in the no-code SDLC flow!
Improvements & fixes
The new Academy: beta environment
The new academy environment now has all functions implemented for its release, our current focus is to align the pages with our branding guidelinesSend an email to odin@bettyblocks.com for Beta access to our new academy environment.
Our current steps are branding and UX implementations, and go-live preparation.
Feature requests
-
- Enhance the Property format reference for numbers and dates article to reflect recent page updates.
- Refine articles that reflect debugging to match the current best practices of debugging
Up next
The Betty Blocks learning management system (LMS)
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 1: LMS Implementation, Branding, and SSO Availability
- Feature: Launch the Academy (based on HubLMS) integrated with Betty Blocks' branding and ensure secure user access through SSO.
- Value: Provides a branded, secure, and accessible platform for users to begin engaging with the LMS while setting the stage for future expansion
Timeframe: We aim to open the environment in January, for the first rounds of customer testing and essential path usage.
- 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.
- 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.
If you would like to leave feedback regarding our content or have any questions about the new LMS, please reach out to odin@bettybocks.com
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!