You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.
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: 14.11.9.5399
This release includes these versions of Blueriq components with a separate life cycle:
Component |
Version |
---|---|
Customer Data Service | 3.4.13 |
DCM Lists Service | 2.0.5 |
Material Theme | 1.0.49 |
Development tools frontend | 1.2.2 |
Document Renderer | 1.1.1 |
4. Aquima Libraries
There are no specific Library updates for this release.
5. Libraries
There are no specific third-party library updates for this release.
6. Retirement announcement
There are no specific retirement announcements.
For a full list of deprecated features, go to Deprecated features.
7. Bug fixes
Identifier |
Component |
Issue |
Solution |
---|---|---|---|
CSD-4263 |
JAVA Runtime |
The XSS JSON Request Body filter would not be applied to requests with a Content-Type header that includes an argument (e.g. 'application/json;charset=UTF-8' |
The XSS JSON Request Body filter will now be applied to any request with a media type that's compatible with the application/json media type. |
CSD-4278 |
|
Due to a restriction placed on the Studio Client by the .NET Framework, it was not possible to render deeply nested validation trees. |
Validation trees are now rendered as indented lists instead of nested trees. These are visually similar while avoiding the restriction. |
CSD-4277 |
|
A recent bugfix in 15.2.1 and 14.11.6 (CSD-4225) has introduced an undesirable project validation error when a library contains multiple process modules |
Validation of message events is no longer done when a library contains more than one root process module |
8. Known issues
For an overview of known issue please refer to: Known issues