You are viewing the documentation for Blueriq 17. 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-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: 17.8.1.315

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

Component

Version

Customer Data Service 5.1.4
DCM Lists Service 4.1.5
Material Theme 1.5.0
Development tools frontend 2.0.2
DCM Maintenance App 5.1.3
Audit Consumer 1.2.3
DCM Dashboard Service 2.2.4
Gateway Service 1.3.2
Document Renderer 2.4.0

3. Blueriq Libraries

For this release there are no specific Library updates.

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 17.8

Version in 17.8.1

logback-classic

ch.qos.logback

Eclipse Public License - v 1.0

1.5.12

1.5.15

logback-core

ch.qos.logback

Eclipse Public License - v 1.0

1.5.12

1.5.15


5. Bug fixes

Identifier

Component

Issue

Solution

BQ-24482

Runtime

CVE-2024-12798 and CVE-2024-12801 were detected on logback 1.5.12 Mitigated by upgrading logback to 1.5.15

CSD-5819

Studio

Studio fields that only contained whitespace would inadvertently become empty when saving.

Whitespace-only values are now read from the XML representation as is, such that whitespace remains as originally specified.

CSD-5808

Studio

The management service did not correctly include the value of ClearBeforeExecute in the data of an AQ_Instance_Update service call.

The ClearBeforeExecute flag is now properly included in the data of an AQ_Instance_Update service call.

6. Known issues

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



  • No labels