beA Desk 1.9 Release Notes

This version is outdated and should no longer be used.

With beA Desk version 1.9 (Client version: 1.9.6; Server version: 1.9.3), new features have been implemented and bugs have been fixed.

Please remember to share the release notes with your staff and colleagues.

Attention: Please review the information under “beA Desk Client no longer creates 0 consumer queues in Rabbit MQ” (section “Bug Fixes”).

Improvements

Update to KSW Toolkit v3.23.0.1

The KSW Toolkit for communication with the KSW interface has been updated to version 3.23.0.1.

This also brings the creation of test protocols up to date.

Optimization of access to the KSW interface

Certain queries to the KSW interface were being executed redundantly, so these have been optimized through caching.

Update of eEB stylesheets

The stylesheets for displaying eEB have been updated to the latest version v351.

Bug Fixes

beA Desk Client no longer creates 0 consumer queues in Rabbit MQ

Since beA Desk version 1.8 Patch, the beA Desk Client mistakenly created an unused persistent queue (LSB) during communication with the DMS. As a result, more and more bus messages accumulated in this queue, which negatively impacted the overall system.

This behavior has been fixed in the current version 1.9. However, any persistent queues already created with the pattern “LEXolutionDmsApiCore.???_[Guid]” must be removed manually.

To do this, follow these steps:

1. Download the “DeleteWrongQueues.zip” archive from the download area.
   
2. Extract the archive on the application server where RabbitMQ (LSB) is running.
   
3. Run the “_execute_me.ps1” script in a PowerShell console.

Alternatively, the mistakenly created persistent queue(s) can also be deleted individually via the RabbitMQ management interface. The names of the queues to be deleted start with the following prefix: **LEXolutionDmsApiCore.???_**

Attachment label can be left blank

The cardinality of the attachment label has been corrected according to the XJustiz specification (“anzeigename”).

The field can now be left blank in the draft view, and the beA message can still be sent successfully.

Incoming messages with attachments without a label are no longer treated as errors.