You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.
1. Upgrade Instructions
The upgrade instructions for this release can be found here.
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.
2. Artifacts
The Blueriq artifacts are available under name: 14.11.21.6048
This release includes these versions of Blueriq components with a separate life cycle:
|
Component |
Version |
|---|---|
| Customer Data Service | 3.4.18 |
| DCM Lists Service | 2.0.9 |
| Material Theme | 1.1.1 |
| Development tools frontend | 1.3.0 |
| Document Renderer | 1.1.1 |
3. Aquima Libraries
There are no specific Library updates for this release.
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
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-19065 |
JAVA RUNTIME |
Vulnerability CVE-2023-24998 was reported for apache.commons-fileupload-1.4.jar |
Fixed the vulnerability by upgrading apache.commons-fileupload to version 1.5. |
|
CSD-4587 |
studio client |
Deleting an element related to a merge conflict could cause an error in the client after a server restart |
The client no longer gives an error in these case, but works as expected |
|
CSD-4573 |
studio client |
Module element parameters, from an external module, could cause an exception in the service call or container editor if the selected external module is not included in an the entry point or an implementation module of the current project |
When such an (invalid) module is selected, the module element selector will be disabled |
7. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools