NewEnhancements| Enhancement | Details |
|---|
| Improved licensing transparency in Encore | Now, based on your license, we clearly indicate which features are not included. UI Indicators: Features that are not part of your license are now marked with a distinct icon in the user interface ( ) Exploration-Friendly: You can still experiment with and create elements that are not included in the license, but they will fail to function in the Runtime. Validation warnings: If you proceed with unlicensed features, you’ll receive validation warnings to inform that the functionality cannot be used in the Runtime.
This update ensures better visibility into your licensing scope, preventing surprises later on. As we have added additional checks to the Studio license file that were only available in the Runtime license file, you may need to update your license-file on the Studio server. Updated license files for the Studio server can be found in the Customers section. |
| | More advanced resizing of decision table cells in Encore | The decision table editor in Encore has been improved to support more resizing scenarios. - Decision table cells now automatically expand in height when entering newlines.
- A cell can be resized in both directions by dragging the bottom right corner.
- The size-to-fit functionality has been expanded to also work for the bottom edge of a cell (resizing the height of the cell) as well as the bottom right corner (resizing the cell in both directions such that the expression fits using a single double click interaction).
| | Business rule editor improvements in Encore | The 'If' - 'then' - 'is' has been made visually more apparent and the target attribute (after the 'then') of a business rule is now preceded with an icon that indicates the data type of this attribute. | | Validation rule editor improvement in Encore | The height of the "message" field in the validation rule editor in Encore has been increased for improved readability. | | New backend for Studio history data | The Studio server achieves its storage of repository history using a separate service, which has been rewritten from the ground up with this release. This is largely transparent to users, but we have observed various performance improvements: - Element history may load significantly faster in large repositories, we've observed improvements from 1s to just 20ms for a single element, for a 50x improvement.
- Branch history loads slightly faster, with an observed 4x improvement.
- Registering changes with many changes may be significantly faster with reduced strain on virus scanners. We've observed cases where this improves performance from minutes to seconds for a single commit operation.
| | Spring Boot 3.4 | Spring Boot has been updated from 3.3.6 to 3.4.3 in the Blueriq Runtime and related components. This introduces newer versions of libraries. If your project has custom code that depends on libraries that come with Spring Boot, you may want to check the release notes from Spring. |
DocumentationDocumentation on the new features and improvements of this release is linked in the respective topics. Upgrade InstructionsSee Release 17.11 Upgrade Instructions for the upgrade instructions for this release. As a best practice - backup your repository
- backup your database before running scripts
- backup your
 directory ([Blueriq installation directory]\Runtime) - backup any config files you have altered under [Blueriq installation directory]\Services
before you start the upgrade. |
Artifacts The Blueriq artifacts are available under name: 17.11.0.434 This release includes these versions of Blueriq components with a separate life cycle: Component | Version |
|---|
| Customer Data Service | 5.2.0 | | DCM Lists Service | 4.2.0 | | Material Theme | 1.5.x | | Development tools frontend | 2.0.2 | | DCM Maintenance App | 5.3.0 | | Audit Consumer | 1.3.0 | | DCM Dashboard Service | 2.3.0 | | Gateway Service | 1.4.0 | | Document Renderer | 2.4.1 |
Blueriq LibrariesThere are no specific Library updates for this release. LibrariesIn this release, the set of third party libraries that is used by Blueriq was updated. When your installation of Blueriq includes custom components (artifacts that do not ship with Blueriq, such as proprietary plugins), those components should be tested for compatibility with these changes. Retirement announcementThere are no specific retirement announcements. For a full list of deprecated features, go to Deprecated features. Bug fixes
Known issuesFor an overview of known issue please refer to: Known issues
| 