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.12.1.1057
This release includes these versions of Blueriq components with a separate life cycle:
Component | Version |
|---|---|
| Customer Data Service | 4.1.6 |
| DCM Lists Service | 2.2.8 |
| Material Theme | 1.1.5 |
| Development tools frontend | 1.5.1 |
| DCM Maintenance App | 2.1.16 |
| Audit Consumer | 0.1.6 |
| DCM Dashboard Service | 0.1.1 |
| Gateway Service | 0.1.4 |
4. 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.
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-19608 | Gateway | After being logged into the dashboard, and refreshing the browser the user is logged out. | The gateway was unable to coupe with multiple Session Cookie headers, due to a dependency removal. This is has been reverted. |
BQ-19528 | Java Runtime | CVE-2023-1370 | Updated net-minidev:json-smart dependency to version 2.4.10 and com.nimbusds:nimbus-jose-jwt to version 9.31 |
BQ-19117 | Gateway | The post logout redirect URI inside the gateway does not handle non-root context environment | When running the gateway inside an environment which is scoped to a specific sub-domain, that is left out of the url when gateway is running on. You can now configure the gateway the blueriq.gateway.post-logout-uri-contextPath property with the contextPath the logout url additional needs to make the correct URI. |
7. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools