You are viewing the documentation for Blueriq 15. 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
For this release there are no specific upgrade instructions.
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.
3. Artifacts
The Blueriq artifacts are available under name: 15.13.12.1782
This release includes these versions of Blueriq components with a separate life cycle:
Component | Version |
|---|---|
| Customer Data Service | 4.1.11 |
| DCM Lists Service | 2.4.5 |
| Material Theme | 1.1.11 |
| Development tools frontend | 1.5.5 |
| DCM Maintenance App | 2.1.24 |
| Audit Consumer | 0.1.12 |
| DCM Dashboard Service | 0.1.7 |
| Gateway Service | 0.1.13 |
| Document Renderer | 1.1.2 |
4. Libraries
5. Retirement announcement
For this release 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-21582 | JAVA Runtime | CVE-2023-34062 affected Reactor Netty HTTP Server lower than 1.0.39 | Updated version of netty Reactor Netty HTTP Server to 1.0.39 |
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-4939 | JAVA Runtime | Performance of AQ-File-Move is slow due to meta data being read twice per kilobyte of the file which is being moved | Added caching so meta data no longer gets read every kilobyte |
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. |
7. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools