You are viewing the documentation for Blueriq 15. Documentation for other versions is available in our documentation directory.
Identifier | Component | Issue | Solution |
|---|---|---|---|
BQ-20266 | Encore | Element actions like Rename and Delete are not allowed inside an external library or when they would affect data inside an externa library. In some cases the buttons for these actions would not be disabled, which caused unwanted behavior. | Disabled buttons for element actions when they can affect data in external libraries or when in scope of an external library. |
CSD-4760 | Encore | Chrome would sometimes give an "loop limit exceeded" warning, while nothing was broken | Updated Encore scroll viewers to avoid this warning from occuring. |
CSD-4752 | Encore | It was possible to make a task mapping without declaring modules. This gave no warnings, yet broke the Runtime. | Changed the modules to 'required' |
CSD-4739 | Encore | When adding a condition below the last condition or when deleting the last condition in a decision table the justifications are removed from the decision table. | Now adding or deleting the columns in a decision table will not affect the justifications. |
BQ-20158 | ProcessFinished Events were not sent via the outbox and could be published to early. | ProcessFinished Events are now sent via the process outbox to make sure events are sent in the right order | |
BQ-20144 | The DCM_ReadCase service is executed in the Case Engine with the application id of the model it is referenced from as input. This application might not have a process engine associated with it. | We do not use the application id during the DCM_ReadCase service execution anymore. We also save the application id used at the intake of a case and use this application id for any interaction with the Case Engine for the case that has been created. | |
CSD-4649, CSD-4582 | '+' characters in query parameters of a Blueriq REST request are encoded when being send. Resulting in a malformed URI when being parsed by Blueriq | '+' characters are now properly encoded to '%2B' before sending the REST request | |
CSD-4627 | Runtime | When using OpenID Connect discovery, it was not possible to configure an URI for the OpenID Connect Provider to redirect to after signing out. | Introduced the blueriq.security.openid-connect.post-logout-redirect-uri property to make the post logout redirect URI configurable. |
Overview
Content Tools