Blueriq 13.12 Bug Fixes

BQ-12371

When retrieving all cases or tasks, first the ids are retrieved and then corresponding cases/tasks. This is unnecessary and leads to more database interactions.

The cases and tasks are now retrieved directly, reducing the number of queries/database interactions.

BQ-12364

The process engine sends updates to the DCM list application. For every update the case is retrieved from the database. This also happened if the DCM list client was disabled leading to unnecessary database calls.

Updated the process engine to only retrieve the case if the DCM list client is enabled.

CSD-3693

The OpenAPI feed of a REST operation could be missing the "responses" field, which is required by the specification.

The "responses" field is now always present to satisfy the OpenAPI specifcation.

CSD-3689

JAVA Runtime

When using Redis with Blueriq, the memory used keeps increasing, even if no actions on the runtime are performed. This ultimately leads to slower or even no response from the runtime over time.

The Redis implemenation of Blueriq kept sessions in memory, even if they were no longer relevant. This caused the memory to grow over time. This has been fixed so the memory is freed again when sessions are no longer relevant.

CSD-3685

When the Process Engine tried to get a lock on a case that has already been locked, a message is written to the log on ERROR level. This should be an INFO message because it does not interrupt the normal program flow.

Changed the log statement from ERROR level to INFO.

CSD-3682

When creating or restoring a backup of studio repositories which is larger than 2GB, an error would occur.

Studio backups which are larger than 2GB can now be backed up and restored using the backup tool.
Using the administration page you can only upload backups up to 2GB, retrieving backups larger than 2GB is no longer a problem.

CSD-3665

When installing Blueriq on a device which doesn't use UTF8 as its default encoding the installation of postgres fails.

We improved the installer to not look at the default encoding used by the device but to enforce UTF8 when initializing postgres

BQ-12100

Flows started in the flow-starter did not appear in the recently started widget.

The issue is fixed: flows will now correctly show up in the recently started widget.

CSD-3655

JAVA Runtime

The datetime picker in the Material theme would fail to render for locales other than en-*.

Missing locale information no longer results in a crash but now correctly shows the datetime picker.

BQ-11935

Development Tools v2

Having a shortcut point to a project with fatal errors caused a server error and no shortcuts were shown at all in the shortcut widget.

The error is now properly handled and displayed on the screen and all valid shortcuts are shown.