You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
1. New
1.1. Difference report in Blueriq Encore
Blueriq Encore will now assist you with comparing different versions of an element using a difference report. This difference report displays additions, deletions, moves, and changes within the element. From this version, the difference report is used for three use cases.
1.1.1. Difference report for merge conflicts
Content and difference conflicts that arise after a branch merge can now be inspected in detail using the difference report. The difference report is available in the bottom drawer in the element that is subject to the conflict. Options to resolve the conflict are offered as well, offering the Business Engineer a smooth workflow.
1.1.2. Difference report for specializations
You can now use the difference report in the bottom drawer of a specialized element to see exactly what has been specialized.
1.1.3. Difference report to inspect pending changes
Up until now, it was only possible to see which elements had been created, deleted, or updated in the list of pending changes. In this version, we have added the possibility of seeing in detail what has been created, deleted, or updated. Simply select the create, delete, or update pill in front of the element name, and the newly added 'Inspect changes' tab will open with the selected element. You will find the difference report here, showing exactly what has been changed. This will be helpful during the review phase.
1.2. Expression evaluator in Blueriq Encore
Verifying the result of an expression given a profile can now be done during design time in Blueriq Encore in addition to the expression evaluator in the runtime. The advantage of evaluating expressions in Blueriq Encore is the availability of the expression editor, which offers autosuggest, syntax highlighting, and real-time validation of the expression.
The expression evaluator is available in the quick test tab in the bottom drawer of the attribute, decision table, business rule, reusable expression, and unit test editor. In the coming minors, functionality within the quick test tab will be expanded.
1.3. Labels in Blueriq Encore
The possibility of editing labels has been added to Blueriq Encore. In addition to Studio, it is now possible to add labels to any type of Blueriq element, including globals and even projects. Labels can be used in the search in Blueriq Encore. Other use-case implementations for labels will be added later.
1.4. Create subflow in Blueriq Encore
To accelerate the refactoring of flows, it is now possible to create subflows from a selection of flow nodes within a flow in Blueriq Encore. Just right-click a flow node after the selection, and the option to create a subflow from it will be offered.
1.5. Document Renderer Service Property Encryption
When configuring properties for the document renderer service one can use the Blueriq Encyptor CLI tool to encrypt any property value in any valid configuration file, environment variable and/or program argument. Consult the proper documentation on a detailed how-to.
Note: It is now required to prepend the 'blueriq.authentication.password' property's value with either {bcrypt} or {noop} and in the case of using bcrypt ofcourse a valid hash.
Document Renderer Service Property Encryption
1.6. Document Renderer Service User Password Hashing
You can hash the password of the credentials used for calling the API using the BCrypt algorithm. One can also choose to not do this by specifying a no operation tag. Consult the documentation for proper use.
Document Renderer Service Authentication Hashing
1.7. Document Renderer Service Health Check Endpoint
You can call "/health" URL to check if the application has fully started and is ready to accept request. The same credentials as any other endpoint on the application must be used.
Document Renderer Service Health Check Endpoint
2. Enhancements
| Enhancement | Details |
|---|---|
| Indication for non-editable modules in Blueriq Encore | Modules that are defined in an external library are not editable. This is now indicated in the list of modules in the navigation panel to inform the Business Engineer about the ability to make changes to the to be selected module. |
| Disabled broswer spell check in Blueriq Encore | We have disabled the browser spell check in Blueriq Encore to prevent confusion between validation errors in the model and the spell check, which both use squiggly red lines under text. |
| Rest service editor optimizations | Based on the selected direction and communication type of a rest service, the location and OpenApi specification description are relevant or not. These properties are now hidden in the rest service editor in Blueriq Encore when they are not relevant, so that they won't unnecessarily distract the Business Engineers attention. |
| Added validation error in Encore | An external library should not be able to have a reference to an internal library. This is now enforced in Blueriq Encore using a validation error. |
| Text in pills in Blueriq Design System is now copyable | It is now possible to copy text from the pill component of the Blueriq Design System. This may, for example, be used to copy information from tags in the history view in Blueriq Encore to the user's clipboard. |
3. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics.
4. Changes Platform Support
Our Platform support is updated.
Changes are:
- Support added for Oracle JRE 21 (LTS) and Azul Zulu OpenJdk 21 (LTS)
- end of support for Oracle JRE 19 and Azul Zulu OpenJDK 19
5. Upgrade Instructions
See Release 16.6 Upgrade Instructions for the upgrade instructions for this release.
As a best practice
- backup your repository
- backup your database before running scripts
- backup your
spring.config.additional-locationdirectory ([Blueriq installation directory]\Runtime) - backup any config files you have altered under [Blueriq installation directory]\Services
before you start the upgrade.
6. Artifacts
The Blueriq artifacts are available under name: 16.6.0.1772
This release includes these versions of Blueriq components with a separate life cycle:
Component | Version |
|---|---|
| Customer Data Service | 4.3.3 |
| DCM Lists Service | 3.0.9 |
| Material Theme | 1.2.2 |
| Development tools frontend | 1.5.6 |
| DCM Maintenance App | 3.0.10 |
| Audit Consumer | 0.3.2 |
| DCM Dashboard Service | 0.2.7 |
| Gateway Service | 0.2.2 |
| Document Renderer | 2.0.1 |
7. Blueriq Libraries
There are no specific Library updates for this release.
8. Libraries
In 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.
9. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
10. Bug fixes
Identifier | Component | Issue | Solution |
|---|---|---|---|
CSD-4972 | Encore | The element history would fail to load for elements that contain the name "Keycloak" due to an incorrect IIS rewrite rule. | The rewrite rule has been adjusted in IIS to avoid a redirect to Keycloak's administation page, allowing the element history to load properly again. |
CSD-4963 | runtime | Traces messages containing properties with a null value cannot be consumed and result an error. | Trace messages containing properties with a null value can now safely be consumed and no longer result in an error. |
BQ-21359 | CVE-2023-46120 affecting spring-rabbit:2.4.15 and lower was detected. | For Blueriq versions 14 up until version 16 we updated the dependency to 5.18.0. For older versions please upgrade to a supported version. | |
BQ-21243 | The DCM Dashboard reverse proxy configuration did not properly rewrite URLs for Blueriq Forms applications. | Updated the rewrite in the DCM Dashboard reverse proxy configuration to support Blueriq Forms applications (see upgrade instructions). | |
CSD-4936 | JAVA Runtime | The runtimeConfiguration endpoint in the Development Tools API would respond with an HTTP 500 status when no config location was set. | The runtimeConfiguration endpoint in the Development Tools API will now work as expected when no config location is set. |
BQ-21122 | Encore | Unknown value in decision table is displayed as an error in Studio, but not in Encore | Studio uses strict equality, whilst Encore uses assignability. This is a correct change, which is why assigning an attribute to unknown still compiles. The related runtime warning has been removed, because the described Runtime behavior was incorrect |
11. Known issues
For an overview of known issue please refer to: Known issues
12. Security notification
Overview
Content Tools