On this page:

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-location directory ([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: 13.13.22.5003

Component	Version
Customer Data Service

There are no specific Library updates for this release.

ArtifactId	GroupId	License	13.13.21	13.13.22
commons-io	commons-io	Apache License 2.0	2.8.0	2.11.0
esapi	org.owasp.esapi	BSD License	2.2.0.0	2.4.0.0
jul-to-slf4j	org.slf4j	MIT License	1.7.32	1.7.36
log4j-api	org.apache.logging.log4j	Apache License 2.0	2.17.1	2.17.2
log4j-to-slf4j	org.apache.logging.log4j	Apache License 2.0	2.17.1	2.17.2
slf4j-api	org.slf4j	MIT License	1.7.32	1.7.36

There are no specific retirement announcements.

For a full list of deprecated features, go to Deprecated features.

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. Additionally, the legacy toggle `blueriq.legacy.use-legacy-case-unlocking` did not properly revert the behavior case unlocking in the process engine to the previous implementation.	A method regarding case unlocking now runs in a database transaction. The legacy toggle was passed improperly to one location where it was used. We now consider the legacy toggle properly.
CSD-4092		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.

For an overview of known issue please refer to: Known issues