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

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

3. Artifacts

 The Blueriq artifacts are available under name: 15.13.37.2838

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

Component

Version

Customer Data Service 4.1.20
DCM Lists Service 2.4.14
Material Theme 1.1.11
Development tools frontend 1.5.6
DCM Maintenance App 2.1.33
Audit Consumer 0.1.20
DCM Dashboard Service 0.1.15
Gateway Service 0.1.23
Document Renderer 1.1.4

4. Libraries

For this release the following libraries have been updated.

ArtifactId

GroupId

License

Version in 15.13.36

Version in 15.13.37

spring-ldap-core

org.springframework.ldap

Apache License 2.0

2.4.1

2.4.4


5. Retirement announcement

There are no specific retirement announcements.

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

6. Bug fixes

Identifier

Component

Issue

Solution

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.

CSD-5603

Runtime

The default mail connection configured via properties conflicted with mail connections when provided by another ConnectionManager. For example when you created your own AquimaConnectionManager or AquimaConnection.

When creating a default mail connection we mark it as default, so it will not conflict anymore with unique mail connections provided from other ConnectionManagers


7. Known issues

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