beA Desk 1.10 Release Notes

Important Notice: Version 1.10 contains a critical bug and has therefore been removed from the download area. Please do not use this version.

beA Desk version 1.10 (Client version: 1.9.6; Server version: 1.9.3) introduces new features and bug fixes.

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

Note: Please review the information under "beA Desk Client No Longer Creates 0 Consumer Queues in RabbitMQ" (see "Bug Fixes" section).

Improvements

Update to KSW Toolkit v3.23.0.1

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

This also brings the generation of test logs up to date.

Optimized KSW Interface Access

Certain queries to the KSW interface were being executed redundantly; these have been optimized through the use of caching.

Update to eEB Stylesheets

The stylesheets used to display eEB have been updated to the current version v351.

Bug Fixes

beA Desk Client No Longer Creates 0 Consumer Queues in RabbitMQ

Since beA Desk version 1.8 Patch, the beA Desk Client was incorrectly creating an unused persistent queue (LSB) during communication with the DMS. This caused bus messages to accumulate in that queue over time, which had a negative impact on 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 so, follow these steps:

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

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

Attachment Labels Can Be Left Blank

The cardinality of attachment labels has been corrected in accordance with 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 that have no label will no longer be treated as invalid.

------------------------------------------------------------------------------------------------------------------
This article has been automatically translated by an AI and may therefore contain errors.

Related to