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

Identifier

Component

Issue

Solution

CSD-3819

JAVA Runtime

In JBoss, the Test Path header would not be read by Blueriq as a (Rest) Service endpoints due to casing issues.

The Test Path header is now obtained by a method that is case insensitive, which makes JBoss read the header properly.

BQ-13168


When installing Blueriq on a machine where .NET framework 4.6.2 is installed the Blueriq Studio Service does not start

Since 13.13.1 and 14.1.1 Blueriq Studio requires .NET framework 4.7.2 as the minimum installed version. This already was the minimum supported version, but was never enforced. The Blueriq installer now verifies if the .NET framework is installed.

BQ-13007


When using DCM 2.0 in conjunction with the DCM Lists Service, the AQ_TaskList would not show that a case was locked in the Material theme, making it look like the tasks of the case could still be started.

The messages to lock and unlock cases are now constructed properly, causing the tasks for a case that is locked to be disabled.

BQ-13005


External Flow sessions were not visible in the development tools. Therefore the profile data, and data of the external flow on the page could not be read by the element selector.

Development tools can now read, and show all the data of External Flow sessions.

BQ-12704


When authentication is required for the application, the development toolbar won't appear after login.

The development toolbar parameter is saved before authentication and retrieved when authentication is succesfull.

CSD-3649


Configuration of Blueriq services where not persistent over minor upgrades

default delivered configuration .yml files of the dcm-lists and customer-data service are now persistent over minor and patch upgrades

BQ-9154


The DCM_TaskList sometimes shows tasks which it should no longer show, or does not show tasks which should be shown.

Fixed a situation in which adding a DCM_TaskList container caused an exception which lead to an event being dropped. Now the event is correctly processed, which allows the task list to properly display the correct tasks.

  • No labels