What to expect?
Improvements to the Error Management in Data Reader Action Group
We’ve introduced new configuration options to provide greater flexibility and control over Data Reader Procedure steps execution when errors occur.
New option in “On error go to group” functionality: “NONE (Continue Procedure execution)”
A new choice, “NONE (Continue Procedure Execution)”, is now available as an alternative to selecting a specific Error Group. When this option is selected, the procedure continues with the next step after an error occurs, maintaining the same behavior as all Board versions up to 14.4 (included). This enhancement allows developers to preserve legacy behavior or opt for more controlled error management as needed.
New flag in the “Error management” group feature: “Get back”
We’ve also introduced the “Get back” flag, available when a specific Error Group is selected. When enabled, this flag allows the Procedure to return to the main flow after performing the actions defined within the Error Group - mirroring the logic already available for If-Then-Else and Go To Group actions.
.png)
Datasets - A New Semantic Layer to Your Data
Datasets is a new Object introduced in this version to enhance self-service capabilities and improve the user experience across the Board ecosystem. Datasets is currently only available for users who are joint Board/Foresight customers.
Designed for business-centric and purpose-specific data access, Datasets enables developers to define a semantic layer that allows users to interact with data without needing to understand the underlying Data Model. Datasets sits on top of the layout editor and provide a simplified, business-focused view of the data.
Datasets allow developers to:
Create structured, purpose-built queries
Empower business users with self-service data exploration
Reuse pre-existing screen layouts as Datasets
Improvements to the Integrated ALM (Application Lifecycle Management) - Transporter enhancements
Datasets are now supported by the Transporter! You can now create, delete, and update datasets across different Data Models or Board environments directly through the Transporter, following the same process used for other Data Model Objects.
A dependency check is automatically performed before creating the transport package, ensuring consistency and preventing conflicts during transport.