You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
1. 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-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: 15.1.1.204
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. Bug fixes
|
Identifier |
Component |
Issue |
Solution |
|---|---|---|---|
|
BQ-16202 |
|
In the DCM Maintenance app's frontend, several vulnerabilities were reported |
We upgraded a lot of dependencies and additionally, we moved one dependency that should not be packaged in the production artifacts to the development dependencies, so that these are no longer shipped as a part of the maintenance app. |
|
BQ-16182 |
|
CVE-2022-30126 detected in Apache Tika |
Upgraded to Apache Tika 1.28.2 |
|
CSD-4117 |
JAVA Runtime |
Unable to upload the same document twice. |
Fixed by clearing the file input value before uploading the next file |
|
CSD-4053 |
JAVA Runtime |
Sending an invalid valuelist value to a BAARS resulted in a 500 http status code, which should be a 400 status code |
When sending an invalid valuelist value to a BAARS it will now send a 400 http status code, with a message that contains the invalid field. |
|
BQ-13004 |
|
When an external flow is started and the page is refreshed, a new session is created and the flow is started again, which may cause instance creation to be executed again. |
When a session already exists in the target container, resume that session instead of creating a new one and starting the flow again. |
6. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools