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

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

Component

Version

Customer Data Service 3.4.9
DCM Lists Service 1.4.7
Material Theme 1.0.42
Development tools frontend 1.1.1

3. Aquima Libraries

There are no specific Library updates for this release.

4. Libraries

No libraries have been updated between version 13.13.16 and version 13.13.17

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

 

Cases are locked in the database when a task is started. Unlocking the case and checking if a case is locked happens by consulting the Hibernate model. We know that Hibernate does not always synchronize with the database when we expect it, which may cause inconsistencies between case being locked/unlocked (a case may appear to be locked while it is not and vice versa).

Like acquiring the lock, unlocking/checking if the lock exists happens through the database instead of Hibernate. Also, when a case is unlocked that was not locked, an exception is thrown indicating this. Lastly, logging was added when a case is unlocked so we can see when this action happens in the log.
 
The changes may result in different behaviour of your application. Specifically, it may be more strict than before, as it is not possible anymore to for instance complete a task with case locking enabled, without a case lock being present. While this is a good thing, know that it is still possible to revert to the legacy behavior using the legacy toggle blueriq.legacy.use-legacy-case-unlocking.

CSD-4037

versionmanagement

Deleting a branch would not allow tags in that branch to be reused again

When a branch is deleted, all tags that correspond with revisions that are specific to that branch are now also deleted.

7. Known issues

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

  • No labels