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



1. Enhancements

EnhancementDetails
AQ_StartProject devtools-bar

When using the AQ_StartProject service to open project in a new window whilst in the context of the devtools-bar, the new window would not open the devtools bar by default.

In Blueriq's angular framework we have added some logic which will add the context when the devtools-bar is available. When using a different frontend framework or if you have extended Blueriq's angular framework check the latest API documentation regarding opening new tabs in the chapter session management.

For projects which still use the MVC theme and have the development tools profile turned on in the Runtime. The AQ_StartProject service will then always append the query parameter devtools to the to be started url.




On this page:

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: 14.3.0.xxxx

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

Component

Version

Customer Data Service3.3.2
DCM Lists Service1.3.5
Material Theme1.0.38
Development tools1.0.3

4. Aquima Libraries

There are no specific Library updates for this release.

5. Libraries

The following third party libraries were changed in this release:

ArtifactId

GroupId

License

Version in 14.2.1

Version in 14.3

jsoup

org.jsoup

MIT License

1.13.1

1.14.2

6. Retirement announcement

There are no specific retirement announcements.

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

7. Bug fixes

Identifier

Component

Issue

Solution

BQ-13441

JAVA Runtime

CVE-2021-37714 was reported on the org.jsoup library which is used by the Runtime.

jsoup was updated to a newer version without the CVE.

BQ-13439


In DCM 2.0, when you would throw a message event with a parameter that doesn't exist in the definition, this would not be logged, making it hard to debug your model.

We now write a log line on level INFO if there are any message event parameters present that are not in the definition.

BQ-13438


When using DCM 2.0, throwing a message event with an expression that results in multiple values would result in an exception.

This has been fixed.

BQ-13431


When merging two branches in Studio, the history screen may fail to show the merge revisions if they are committed within less time than the number of hours offset from UTC. This prevented the ability to actually merge, as you need to select a merge revision to complete the merge.

Revision dates are now consistently processed in UTC, enabling accurate filtering of revisions.

BQ-13426


When the aggregate version attribute parameter was empty in a DCM_CaseCreate service call, an exception would occur.

This was fixed by ignoring the version attribute in the case engine if it was not set.

BQ-13334


When using DCM 2.0, automatic tasks after completion of another task would be executed on the Case Engine instead of on the Runtime that was configured for Task Execution.

The task is now executed on the Runtime for Task Execution again.
Note: Automatic tasks that are the result of a message event or of a timer will still execute on the Case Engine. We are planning to address this in the near future.

CSD-3830

versionmanagement

Merging branches in Studio could fail when an element had been renamed.

The failure that occurred when renaming an element has been resolved, allowing the merge to succeed.

CSD-3824

JAVA Runtime

The reverse proxy which is configured by default when using the Blueriq Installer, didn't pass the right headers for https to work.

Added the header to the reverse proxy configuration for IIS when installing Blueriq with the installer.

BQ-13240


When the H2 console is enabled and the path to its properties directory contains spaces, property files may be saved in a directory where '%20' is used instead of real spaces

Replace '%20' by real spaces for the H2 console properties directory

CSD-3795
In some cases boolean values where not shown properly due to casing differencesCasing for boolean values is now ignored in some places

CSD-3786

JAVA Runtime

When performing a reload session/project in the development toolbar an error could be shown that an entity instance with a particular id could not be found (anymore)

All entity instances will be properly refreshed after a reload session/project is performed

8. Known issues

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