You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
1. Documentation
Documentation on the new features and improvements of this release is linked in the respective topics
2. Upgrade Instructions
There are no specific upgrade instructions for this release.
As a best practice
- backup your repository
- backup your database before running scripts
- backup your
spring.config.additional-location
directory ([Blueriq installation directory]\Runtime) - backup any config files you have altered under [Blueriq installation directory]\Services
before you start the upgrade.
3. Artifacts
The Blueriq artifacts are available under name: 16.11.4.2403
This release includes these versions of Blueriq components with a separate life cycle:
Component |
Version |
---|---|
Customer Data Service | 4.5.4 |
DCM Lists Service | 3.1.4 |
Material Theme | 1.3.3 |
Development tools frontend | 1.7.0 |
DCM Maintenance App | 4.1.6 |
Audit Consumer | 0.5.5 |
DCM Dashboard Service |
1.1.4 |
Gateway Service | 0.4.6 |
Document Renderer | 2.2.0 |
4. Libraries
For this release there are no specific Library updates.
5. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
6. Bug fixes
Identifier |
Component |
Issue |
Solution |
---|---|---|---|
CSD-5356 |
Java Runtime |
Executing a SOAP request without an active tracing context would fail with a NullPointerException. |
The tracing context is not incorrectly propagated when none is active. |
BQ-23297 |
Encore |
Copy to clipboard from quick test would not copy date and datetime values correctly. |
Date and datetime values are now formatted using ISO-8601 notation. |
BQ-23292 |
Encore |
The scroll position of navigation menus was not remembered once the navigation menu had been closed. |
Opening the navigation menu now restores the scroll position according to the previous time the navigation menu was open. |
BQ-23277 |
Java Runtime |
The mapping for the external flow contract that was introduced in Blueriq 16.10 would not properly detect of an attribute was single valued or multi valued, which would case problems when the mapping contained multi valued date or date time attribute containing a single value. |
The external flow mapping now properly detects the multivalued state of the attribute |
CSD-5346 |
Encore |
The REST editor did not provide body elements or custom schema elements for the request body when using an XSD schemaset. |
The available elements can now be selected again from the dropdown. |
BQ-23257 |
|
The OutboxTraceDao would log a warning on every case action about not being able to trace an aggregate event becasue of a missing case id. |
When the OutboxTraceDao receives a Aggregate event it is now dropped immediately and logging it on DEBUG level instead of WARNING level. |
BQ-23254 |
|
The mapping for the external flow contract that was introduced in Blueriq 16.10 would populate instances before all instances have been created, which would cause problems when the mapping would contain relations. |
The external flow mapping now creates all instances before starting to populate them. |
CSD-5342 |
Encore |
An expression editor that is not initially visible, e.g. when it is shown in a tab that isn't open when opening an editor, and has validation errors/warnings would remain invisible until the window is resized. This occurred only when using Chrome, using Firefox behaved as expected. |
The expression editor now properly resizes itself when becoming visible, such that the expression is shown without needing to resize the window. |
BQ-23196 |
Java Runtime |
Using external flows with in memory session management is not possible and results into errors when trying to start a session |
Due to a spring boot upgrade external flows and the key-value redis store components where tightly coupled. This has been decoupled and should work independently again. |
CSD-5324 |
|
Hibernate would use camelCased column names by default when interacting with the database whilst the delivered database scripts would create column names in lowercase. which can lead to errors when using a database that is not case insensitive. |
Fixed this making the column names of entities lowercased. |
CSD-5302 |
Java Runtime |
When using |
The REST service client will now fail with the field validation's message instead of failing with an unexpected exception. To fully disable including field validations for REST responses, the new legacy toggle |
CSD-5221 |
|
When getting hibernate properties for the sql stores, we would iterate multiple times over all available properties to filter out hibernate properties. |
Fixed this by checking if a property is relevant and immediatelly processing it. |
7. Known issues
For an overview of known issue please refer to: Known issues