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

Identifier

Component

Issue

Solution

CSD-3947

JAVA Runtime

When starting a child session via the AQ_StartProject service with a configured test path. The service calls in the started project's flow, which are before the first page, are not affected by the propagated test path.

We have resolved the issue by copying the test configured test path onto the child's session before the flow is started.

CSD-3943

JAVA Runtime

The development dashboard won't display projects when two published models have the same export date.

When two published models contain the same branch name and export date but different revision the new development dashboard was not able to distinguish them and it resulted into an error when loading the projects. This has been resolved.

CSD-3946


A domain schema preview in Studio would fail if the target entity of a relation did not have the same capitalization as the entity's definition name.

The target entity name of a relation is now used in a case-insensitive way.

CSD-3941

JAVA Runtime

Fields did not properly supported domains with invalid domain options

Corrected the code to handle invalid domain options in the correct way

CSD-3923

JAVA Runtime

When reloading a project where the flow contains an active instance of a singleton entity, an instance id mismatch error is thrown.

When reloading a project the previous state of the active sessions is transferred onto the newly created sessions. While transferring the profile, new singletons instances were created. Resulting in new instance ids for which causes the mismatch. This is resolved by reusing the old instance id, which was already the case for multiton instances.

BQ-13195


For BAA(R)S endpoints that have a shortcut, the test path would always be read from the HTTP request, even in production mode. Test Paths are a development only feature.
If test path properties were present for the shortcut of the BAA(R)S, an attacker could provide a X-Blueriq-TestPath header and a different branch than the intended branch would be used to execute the BAA(R)S service.

Test path properties will now be ignored when running Blueriq Runtime in Production Mode.

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