beA Desk 1.9 Release Notes

With version beA Desk 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 distribute the release notes to your employees and colleagues.

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

Enhancements

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 updates the generation of test protocols to the latest state.

Optimization of accesses to the KSW interface

Since certain queries to the KSW interface were redundantly executed, these have been optimized using 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 DMS. As a result, more and more bus messages accumulated in this queue, negatively affecting the overall system.

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

Please proceed as follows:

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

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

Attachment designation can remain empty

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

Thus, the field in the draft view can remain empty, and the beA message can still be sent successfully.

Incoming messages with attachments without a designation are no longer received as erroneous.