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

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

Component

Version

Customer Data Service5.0.4
DCM Lists Service4.0.3
Material Theme1.3.4
Development tools frontend2.0.1
DCM Maintenance App5.0.6
Audit Consumer1.0.5
DCM Dashboard Service2.0.3
Gateway Service1.1.1
Document Renderer2.2.2

3. Blueriq Libraries

ArtifactId

GroupId

License

Version in 17.4

Version in 17.4.1

aspectjweaver

org.aspectj

Eclipse Public License - v 2.0

1.9.22

1.9.22.1

micrometer-commons

io.micrometer

Apache License 2.0

1.12.5

1.12.9

micrometer-core

io.micrometer

Apache License 2.0

1.12.5

1.12.9

micrometer-jakarta9

io.micrometer

Apache License 2.0

1.12.5

1.12.9

micrometer-observation

io.micrometer

Apache License 2.0

1.12.5

1.12.9

netty-buffer

io.netty

Apache License 2.0

4.1.108.Final

4.1.112.Final

netty-codec

io.netty

Apache License 2.0

4.1.108.Final

4.1.112.Final

netty-common

io.netty

Apache License 2.0

4.1.108.Final

4.1.112.Final

netty-handler

io.netty

Apache License 2.0

4.1.108.Final

4.1.112.Final

netty-resolver

io.netty

Apache License 2.0

4.1.108.Final

4.1.112.Final

netty-transport

io.netty

Apache License 2.0

4.1.108.Final

4.1.112.Final

netty-transport-native-unix-common

io.netty

Apache License 2.0

4.1.108.Final

4.1.112.Final

spring-aop

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-aspects

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-beans

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-context

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-context-support

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-core

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-expression

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-jcl

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-jdbc

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-messaging

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-orm

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-oxm

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-tx

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-web

org.springframework

Apache License 2.0

6.1.6

6.1.12

spring-webmvc

org.springframework

Apache License 2.0

6.1.6

6.1.12


4. Bug fixes

Identifier

Component

Issue

Solution

CSD-5495

Java Runtime

When the Runtime needed to sort a list of instances in the profile, for example the instances in a repeat flow, and the set of attribute values would contain duplicate values, the Runtime could give an error: "Comparison method violates its general contract".

Instances are now sorted according to their creation ordering for the ones with an equal sort attribute.

BQ-23702


CVE-2024-38808 and CVE-2024-38809 were reported on the spring library used by the studio backup tool

Updated spring to a version containing fixes for the CVEs

CSD-5466

Encore

Dropdown panels could be positioned off screen such that not all options could be selected.

Dropdowns are now sized to always fit within the viewport, both horizontally as well as vertically.

BQ-23601


When two actions happen on a single case right after each other, the process outbox could be read concurrently by two threads. This could result in error messages when a message would be removed by the one thread while it's already removed in another thread.

The situation described is perfectly valid, the second removal of the message is now ignored. The error message has been replaced by a debug message stating that the message was already removed.

5. Known issues

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