You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.

This release contains a bug that affects you if you have enabled the external-flow profile. In that case, we recommend you to not use this version, but use 14.11.6 or newer.

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:  14.11.4.5111

This release includes these versions of Blueriq components with a separate life cycle:

Component

Version

Customer Data Service 3.4.13
DCM Lists Service 2.0.5
Material Theme 1.0.47
Development tools frontend 1.1.3
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.

ArtifactId

GroupId

License

Version in 14.11.3

Version in 14.11.4

tika-core

org.apache.tika

Apache License 2.0

1.26

1.28.2


5. Bug fixes

Identifier

Component

Issue

Solution

BQ-16182

JAVA Runtime

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-4110

JAVA Runtime

If a portal message was thrown inside an external flow, the flow would revert to a regular flow, not sending its exit event back to the host runtime.

After throwing a portal message, the external flow now remains external and sends its result to the host properly.

6. Known issues

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