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

Identifier

Component

Issue

Solution

CSD-3795

 

The studio could fail to display boolean values correctly if they were stored using an unexpected capitalization.

The studio now normalizes values to interpret their boolean value correctly.

BQ-12772

 

Wen using the DCM Lists Service as the source for the work list or task list, sometimes a task is shown for a user, while this task requires a role which the user does not have. This is because events were sent when a task was created, before the authorization info was added by the authorization algorithm.

DCM list events for tasks that are created are now sent after the authorization info has been added, so they can be properly routed to the users that have the correct authorization.

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.

BQ-12512

 

If no Blueriq license could be found, the runtime would fail with a NullPointerException.

We fixed this. Now, the runtime will still not start when no license is present, but it will explain why.

BQ-12346

 

If the session manager was configured to use an external session store (Redis), the Blueriq license would be checked on each request, which is bad for performance.

The Blueriq license is now only checked during startup of the runtime.
  • No labels

Didn't find the answer you were looking for? Try the advanced search!