November 25, 2024
While transitioning to a new documentation and education environment, you may also expect new features, like signing up to receive our release notes via email.
Scroll to the bottom of this article, add your email to the sign-up form, and be one of the first to get notified about release notes!
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
Resolved issue when selecting input variables in page variable filtering
Value: Page variable filtering has been updated to resolve an issue when trying to select input variables on the right-hand side of the filter. Previously, the select button to insert the input variable remained disabled making it impossible to use it. This bug has now been fixed, allowing you to use input variables in page variable filtering again.
Impact: Users do not need to take any additional steps to benefit from this fix.
Enhanced entity browser for display logic filtering
Value: The entity browser used in display logic filtering has been enhanced when using page variables.
Previously, selecting a model property could inadvertently allow the selection of an entire page variable item. This caused an infinite loading issue after clicking "select". To resolve this, selecting an entire page variable item is no longer permitted in the display logic filtering. Instead, clicking a page variable item now automatically drills down to its model properties, enabling faster and more efficient navigation.
Impact: Users do not need to take any additional steps to benefit from this fix.
Custom font family option for data table pagination text
Value: The data table component now includes the ability to customize the font family used in the table’s pagination section. Previously, the pagination text defaulted to our standard “Roboto” font, with no option for customization. With this update, builders can select a text style of their choice, allowing the font family from that style to be applied to the pagination text. This enhancement provides greater flexibility and ensures consistency with your desired design aesthetics.
Impact: This improvement is only available in the latest version of the data table component in the default Betty Block component set. Existing components already in use on pages will not automatically receive this improvement.
Enhanced CLI validation for empty string component option values
Value: The Betty Blocks CLI (Command-Line Interface) used for developing custom components has been updated to prevent issues caused by using empty strings ("") as option values. Previously, building a custom component with empty string option values could lead to unexpected behavior when using the component in the page builder IDE. With this update, the build process will now fail if invalid option values, such as empty strings, are detected. The CLI does even validate the type of an option now, which is even more helpful for users. This proactive validation helps developers catch issues early, ensuring better and more reliable component development.
Impact: Users need to update the CLI version to at least V25.99 to benefit from it.
Up next
Synchronizing form action create or update step when form changes
Value: This feature introduces automatic synchronization for create and update action steps when modifying the create or update form components. When changing a form - such as adding or removing inputs bound to model properties - will be automatically reflected in the corresponding create or update action step, eliminating the need to manually adjust these action steps. This streamlines form updates and saves time.
Impact: The impact of this feature are twofold:
- Newly added forms: This synchronization feature will be enabled by default for newly added create or update form components from the default component set after the release. Users can start benefiting from automatic updates without any additional setup.
- Existing forms: For forms already added to pages after the release, this feature will be optional, allowing users to opt in if desired. Detailed instructions on how to enable synchronization for existing forms will be provided in the official release documentation.
Timeframe: December 2024
New “add form input” option on form components
Value: We will 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: December 2024
Save as widget
Value: As a builder I can save an Empty widget as a widget.
Impact: When this is released the wrapper component will contain a 'Save as' option that allows builders to save their Empty widget as a widget. After saving, the new widget or component is visible in their respective category. That also means a new category 'widgets' is added next to components and partials in the sidebar.
Want to try it out already? Contact the product owner, Manouk van Gerwen, to get the feature flag to enable this feature (manouk.van.gerwen@bettyblocks.com).
Timeframe: Q4
Data
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.
Up next
Dependency checker for properties (Beta)
Value: We are excited to introduce a new feature to enhance the user experience when managing properties within the platform. Previously, when users deleted a property, the platform didn’t provide insights into where that property was being utilized. This often led to broken pages or actions, creating uncertainty and reducing confidence in performing safe deletions. In the detail view of a property, users will now see a new tab titled "References". This tab provides clear visibility into where each property is being used across the platform, including dependencies within pages, models, and actions.
Impact: Since this is a Beta feature, you need to apply a feature flag to gain insights into the dependencies of properties which will be provided on request.
Timeframe: Within the upcoming month.
Actions
Improvements & fixes
Current authenticated user in sub action
Value: Previously, the authenticated user details got lost when using an authenticated sub action. With the new fix, the builder can access the webuser details in a sub action again.
Impact: No action needed from the builder side.
Updates to the following action steps
- Log step (native)
Value: Previously, the builder needed to select the severity within the log step. Now, it has default severity ‘debug’, leading to less clicks the user needs to make when using the log step. - HTTP(S) step (native)
Value: In the new version of the HTTP step, the builder is able to set a response code for the output. With it, you can read the response code from the HTTP request next to the response body. - Date-time-offset
Value: Now, the builders have the ability to calculate with business days only. Simply activate this functionality via the toggle.
- Expression step
Value: The expression step now has the option to set the output to array. With this, the builder can give next to a text, boolean and number, an array type as an output of this step.
Impact: To make use of the new versions of the steps, the builder needs to drag the new step onto the canvas and re-configure the options.
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.
In the upcoming months, we are rolling out a series of updates to enhance the debug logging experience, broken into four key milestones:
- Milestone 1: 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.
- Milestone 2: 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.
- Milestone 3: Advanced filtering options
- 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
- Milestone 4: Loop step logging
- Feature: Enables logging for the loop steps
- Value: Provides a clear overview of the logs for the loop steps.
Impact: Users do not need to take any additional steps to benefit from these improvements.
Timeframe: The first two milestones are expected mid-December 2024
My Betty Blocks
New features
Expand tables on company overview
Value: As a company admin, I want to have a full width option for the tables in the company overview, so that I can utilize my large screen to view all data at once.
Impact: On the different tables in the company overview there is now an expand table button available in the top right corner of the table.
Improvements & fixes
Company overview view permissions
Value: Company dashboard, organizations, applications and templates are no longer visible for users that did not have the permissions to view these tables.
Impact: Resolved a bug where company members were able to view certain company data without having the correct permissions.
Company overview switcher
Value: Unable to see companies in the dropdown to select a company where there are no view permissions.
Impact: Users that have a membership with multiple companies were able to see companies they did not have the view permissions for.
Up next
Master Templates (Beta)
Value: As an organization admin, I want to have a master template, so that applications created based on this template can receive updates after changes have been made.
Impact: Promotion of an application to a Master Template can be done via the Applications Template settings. Currently, this is behind a feature flag; please let us know if you want to check out this feature.
Timeframe: In the upcoming 2 weeks.
Audit Logging
Value: Company members with the view audit logging permission are able to see logging of important events providing a detailed history of actions performed for security, compliance, and troubleshooting in the case of an incident
Impact: The audit logging will be available as a new page on the company overview page.
Timeframe: In the upcoming 2 weeks.
Company Builders
Value: Show the total amount of builders associated with the company so that the company admin can see the potential impact on the billing based on builders. Betty Blocks users will not be counted towards the total number of builders.
Impact: The total number of builders will be displayed on the company overview dashboard.
Timeframe: in the upcoming 4 weeks.
Education
New documentation environment!
The environment in which you are reading this article will soon be updated to also be reachable via docs.bettyblocks.com
-
Refined navigation & branding
-
Currently testing and refining the AI chatbot
Filtering logic reference
Learn how to apply filtering logic in the platform by reading our new article.
Improvements & fixes
Multiple small updates to support interaction changes
- Clear interaction on rich text component now available
Up next
Improvements to 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.
We have decided to work together with the HubLMS team to bring our LMS to a higher level and keep your eyes open for wonderful and exciting environmental changes.
Timeframe:
-
New LMS enabled, end of Q4
If you would like to leave feedback regarding our content and way of learning the platform, 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!