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.0.1.130
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-16019 |
JAVA Runtime |
CVE-2022-24891 was reported on the esapi third party library. |
We updated the esapi library to version 2.4.0.0, which doesn't contain the vulnerability. |
|
BQ-15973 |
JAVA Runtime |
CVE-2022-23457 was reported on the esapi third party library. |
We updated the esapi library to version 2.4.0.0, which doesn't contain the vulnerability. |
|
CSD-4098 |
JAVA Runtime |
In certain circumstances, where the process engine was called directly from custom code, unlocking a case would lead to an exception. |
A method regarding case unlocking now runs in a database transaction. |
|
CSD-4092 |
Studio |
The name of a repository and branch was inadvertently limited to 50 characters, which should have been 100 characters instead. |
Repository and branch names can now be 100 characters again, aligning with the validation that is done by the Studio client. |
|
BQ-15691 |
JAVA Runtime |
Since the spring boot upgrade to version 2.6 a circular dependency error would be raised if the case-engine-client profile is active. |
Moved ILicenseProvider bean into own config file to make the AquimaConfig not dependent on it and thus breaking the cycle. |
|
CSD-4007 |
JAVA Runtime |
When the system's hostname could not be determined during startup, the runtime would not start. |
The runtime will now continue, even if it cannot determine the hostname. In this case, it will use an empty hostname and domain for the license check. |
7. Known issues
For an overview of known issue please refer to: Known issues
Overview
Content Tools