You are viewing the documentation for Blueriq 15. 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: 15.13.36.2770
This release includes these versions of Blueriq components with a separate life cycle:
Component |
Version |
---|---|
Customer Data Service | 4.1.20 |
DCM Lists Service | 2.4.14 |
Material Theme | 1.1.11 |
Development tools frontend | 1.5.6 |
DCM Maintenance App | 2.1.33 |
Audit Consumer | 0.1.20 |
DCM Dashboard Service | 0.1.15 |
Gateway Service | 0.1.23 |
Document Renderer | 1.1.4 |
4. Libraries
For this release the following libraries have been updated.
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 |
---|---|---|---|
BQ-24217 |
|
CVE-2024-47535 was reported on netty-common |
Fixed CVE-2024-47535 by upgrading netty-common to 6.1.155.Final |
CSD-5757 |
Encore |
The REST service editor would inadvertently interpret request attributes as required, even if they weren't. |
The default value of the required state was misaligned between Encore and the Studio server backend, which has been corrected. |
CSD-5683 |
Studio |
Using the Management Service to retrieve revision changes would fail if a data mapping test case is present as pending change. |
Data mapping test cases no longer result in a failure of the GetRevisionChanges SOAP action. |
CSD-5675 |
Encore |
The data mapping editor would show an Accept button for unexpected attribute values, but this button wouldn't do anything when the instance itself had not been created yet in the expected profile. |
The instance is now created in the expected profile as necessary. |
7. Known issues
For an overview of known issue please refer to: Known issues