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

1. Upgrade Instructions

For this release there are not specific upgrade instructions.

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.33.6426

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

Component

Version

Customer Data Service 3.4.23
DCM Lists Service 2.0.11
Material Theme 1.1.3
Development tools frontend 1.3.1
Document Renderer 1.1.1

3. Libraries

ArtifactId

GroupId

License

Version in 14.11.32

Version in 14.11.33

JavaEWAH

com.googlecode.javaewah

Apache License 2.0

1.1.13

1.2.3

org.eclipse.jgit

org.eclipse.jgit

EDL

5.13.1.202206130422-r

6.6.1.202309021850-r

4. Retirement announcement

For this release there are no specific retirement announcements.

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

5. Bug fixes

Identifier

Component

Issue

Solution

BQ-21064

Audit Consumer, JAVA Runtime

CVE-2023-4759 was detected for Eclipse JGit lower than 6.6.1.

Fixed by updating Eclipse JGit to version 6.6.1

BQ-20080

JAVA Runtime

Debug logging is polluted with unrecognizable stack traces which cannot related to the an actual failure for the AbstractSessionAwareFilter

Additional logging was added to determine whether exceptions that occurred during the logic of the AbstractSessionAwareFilter were recoverable and relatable to actually errors. It seem that they were not and therefore the logging is removed.

CSD-4499

JAVA Runtime

When defining the following property connection.restservice.http.header.auth-header in a application.properties file and in a second property file which is activated by a profile. The property from the application.properties was picked up instead the one declared in the profile properties file.

Reading certain properties, for instance header properties for http connections, did not follow the property overloading mechanism which was expected.
We have fixed this behavior and properties are now loaded in their ordered precedence.

6. Known issues

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


  • No labels