Fixed bugs in KMD WorkZone 2023.0

Mass Dispatch: Misleading error message

Bug number ALM 177
Description A misleading error message was shown when the case handler did not have sufficient rights to approve a mass dispatch.
Correction Fixed

Mass Dispatch: Searching for a case group in the Start mass dispatch dialog failed

Bug number ALM 190
Description Sometimes, searching for a case group in the Start mass dispatch dialog failed because the search text was case sensitive.
Correction Fixed

Mass Dispatch: Canceling a mass dispatch while letters were being generated locked the case and documents

Bug number ALM 199
Description It was not always possible to cancel a mass dispatch process. It depended on where in the workflow in the process was.
Correction If it is not possible to cancel a mass dispatch process, a warning is shown saying that it is not possible to cancel right now. When the cancelation is successful, the write access code on the case and the generated documents is removed.

Mass Dispatch: Cases and documents were locked because of the ALLEENMER&SJPROCESSUSER access code

Bug number ALM 217
Description Generated cases and documents were locked because the ALLEENMER&SJPROCESSUSER write access was kept.
Correction When a Mass Dispatch process finishes successfully. it removes the write access code on generated documents and the used case.

Mass Dispatch: Missing information about documents in the mass dispatch

Bug number 217073
Description The mass dispatch history document was missing information about the documents that were included in the mass dispatch.
Correction The documents that are included in the mass dispatch after validation and approval are now shown in the history document.

Mass Dispatch: Some error messages were in English in the Danish version

Bug number ALM 126
Description Some error messages were in English in the Danish version.
Correction Fixed

Mass Dispatch: The history document did not include documents if the validation was repeated several times

Bug number ALM 220
Description When accepting a mass dispatch after three attempts to validate the recipient list, the documents in the mass dispatch were not shown in the history document.
Correction Fixed

Mass Dispatch: The mass dispatch timed out after validation

Bug number ALM 224
Description Mass dispatch timed out after validation.
Correction The process that cleans up the database for recipients that are not validated OK has been changed to clean up recipients in small batches instead of one large clean-up that times out.

Mass Dispatch: The Start mass dispatch dialog did not show the default excluded CPR status codes

Bug number ALM 208
Description The Start mass dispatch dialog did not show the default excluded CPR status codes that have been configured for the Mass dispatch process in WorkZone Configurator.
Correction Fixed.

Mass Dispatch: The Start mass dispatch dialog included deactivated party roles

Bug number ALM 195
Description activate document party roles were shown and available for selection in the Start mass dispatch dialog (Recipient tab > Party role field). The mass dispatch process failed if a deactivated document party role was selected.
Correction Only active document party roles are shown in the Party role field on the Recipients tab.

Mass Dispatch: Wrong icon for canceled process in Processes overview

Bug number ALM 202
Description The icon for canceled mass dispatch processes was wrong in the Processes overview.
Correction Fixed.

Mass Dispatch: Wrong icon for canceled processes in the ribbon

Bug number ALM 202
Description The icon for canceled mass dispatch processes was incorrect in the ribbon of the Processes tab.
Correction Fixed.

Mobile: WorkZone Mobile app only shows the 50 oldest case documents

Bug number CS1789108
Description WorkZone Mobile app shows the oldest case documents first, and can only show 50 documents. Meaning that it only shows 50 oldest case documents, so for cases with many documents consultants cannot see the latest documents at all.
Correction Case documents are now displayed starting with the newest documents, and users can navigate to the next or previous page of a case documents list to see all documents on each case.

SmartPost: Asynchronous receipts resulted in an error message

Bug number ALM 150
Description Asynchronous receipts resulted in a “SmartPost was unsuccessful” message The timeout for process cannot be configured to a different value than 5 min.
Correction Now the timeout process can be set up in the database as a customization, with the number of retries and delay between them controlled from wzp_error_manager. You can configure how many times SmartPost will try to receive the business receipt and at what intervals in the error manager. By default, for each dispatch (recipient) in a SmartPost dispatch, up to 180 attempts will be made to receive a business receipt, with a 10-second pause between each attempt."