Released hotfixes for WorkZone 2022.2

2022.2 HF01

Incorrect error message in Danish when sharing too many list items

TFS Number 211351

This hotfix corrects the error message in Danish, displayed when users try to share too many list items.

2022.2 HF01

Not published

This hotfix was not published and is only listed here to ensure no gaps in the hotfix numbering sequence.

2022.2 HF02

Adding multiple documents to be moved with the original document cased an error

TFS Number 209653

In WorkZone Client, when moving a document from one case to another, a blocking error occurred when expanding the drop-down list in the Move to case field of the Move documents form. This prevented adding more documents to be moved with the original document. Now, multiple documents can be added when moving a document to another case.

SCIM could fail provisioning of parallel request from Microsoft Azure

TFS Number: 209954

SCIM could fail provisioning of parallel requests from Microsoft Azure. The issue could potentially occur when provisioning many users or groups. The provisioning failed and nothing was created in WorkZone. This has been fixed.

2022.2 HF03

Access codes not displayed in access code drop-down lists for WorkZone Cloud Edition using SCIM Provisioning

TFS Number 210809

On WorkZone Cloud Editions operating with Microsoft Azure Active Directory and using SCIM provisioning to provision users from Microsoft Azure Active Directory to WorkZone, access codes assigned to users were not displayed in access code drop-down lists. This was caused by the inactive field in the access_code domain not being set correctly for access codes replicated from Microsoft Azure Active Directory. Now, access codes assigned to users are displayed correctly in access code drop-down lists.

2022.2 HF01

Unable to create a new case with Term access code/Organizational access code (Emneindblik/Organisatorisk indblik)

TFS Number: 215749

When creating a new WorkZone case using the WorkZone for Office add-in in Microsoft Outlook/Word/Excel/PowerPoint, adding values to the Term access code and Organizational access code (Emneindblik/Organisatorisk indblik) fields resulted in errors, making it impossible to create a case, if Term acess code or Organizational access code values were required.

This issue was related to a customer-specific customization. It has been corrected.

Errors with case list requests containing more than 1000 columns

TFS Number: 209583, INC4389706

Case list requests containing more than 1000 columns in a query were resulting in errors.

Corrected.

2022.2 HF02

REM 828004: Attaching documents from historical databases as email attachments works incorrectly

Sharing documents from historical databases by sending them as email attachments from WorkZone Client does not work correctly (wrong document with the same ID from the production database is attached instead. If there is no document with such ID in the production database, no documents are attached at all).

Corrected.

In addition, this hotfix contains improvements for multiple database support in WorkZone for Office add-in (opening documents, saving documents and emails, WorkZone Process integration and so on).

2022.2 HF03

Word closes unexpectedly

REM 836822, TFS 241214.

Word application is crashing when trying to create a Word document from WorkZone Client.

This was caused by a conflict between WorkZone for Office add-in and the customer’s customized Templafy add-in.

Correction: The two add-ins no longer conflict and Word will not crash.

2022.2 HF01

REM 829909/222524: WorkZone PDF Crawler stops running due to a memory leak

WorkZone PDF Crawler stopped running due to a memory leak.

To solve this issue, the Aspose.PDF library has been upgraded to Aspose.PDF for .Net 22.10, which contains performance improvements related to memory consumption.

2022.2 HF01

Random number of mass dispatch processes fail due to incorrect processing of receipts

211668/ALM 206

Under some circumstances when receiving lists of receipts from NgDP, the receipts were not processed correctly in WorkZone, which caused the mass dispatch process to get stuck waiting for receipts that had already been received.

Corrected.

Malfunctioning Approve button and misaligned label and check box in the Approve mass dispatch task/smartmail

214531

In the Approve mass dispatch task/smartmail, the Releasable to Internet Transmission label was not aligned with the corresponding check box, and the Approve button did not function correctly.

Both issues have been corrected.

SmartPost messages with empty attachments were not received in WorkZone

INC4563632/INC4629846

SmartPost messages with empty attachments were not saved in WorkZone because it is not possible to save "empty" files in WorkZone, and therefore the messages would become stuck at NgDP.

This hotfix ensures that if WorkZone receives a message with empty attachments (attachments with the length 0) from NgDP, WorkZone will not try to save the empty attachments. However, WorkZone always attaches a document named MemoMessage, which contains information about the content of the entire dispatch showing the name and length of all attachments in the dispatch.

2022.2 HF02

Mass dispatch: Misleading error message

205735/ALM 177

 A misleading error message was shown when the case handler did not have sufficient rights to approve a mass dispatch.

Corrected.

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

205733/ALM 190

Sometimes, searching for a case group in the Start mass dispatch dialog failed because the search text was case sensitive.

Corrected.

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

211348/ALM 199

It was not always possible to cancel a mass dispatch process. It depended on where in the workflow in the process was.

Now, 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

216520/ALM 217

Generated cases and documents were locked because the ALLEENMER&SJPROCESSUSER write access was kept.

Now, 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

217073

The mass dispatch history document was missing information about the documents that were included in the mass dispatch.

Now, 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

217093/ALM 126

Some error messages were in English in the Danish version.

Corrected.

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

216365/ALM 220

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.

Corrected.

Mass dispatch: The mass dispatch timed out after validation

216412/ALM 224

Mass dispatch timed out after validation.

Now, 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

213299/ALM 208

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.

Corrected.

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

211285/ALM 195

Deactivated 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.

Now, 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

211363/ALM 202

The icon for canceled mass dispatch processes was wrong in the Processes overview.

Corrected.

Mass dispatch: Wrong icon for canceled processes in the ribbon

211362/ALM 202

The icon for canceled mass dispatch processes was incorrect in the ribbon of the Processes tab.

Corrected.

SmartPost: Asynchronous receipts resulted in an error message

200930/ALM 150

Asynchronous receipts resulted in a “SmartPost was unsuccessful” message The timeout for process cannot be configured to a different value than 5 min.

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, up to 180 attempts will be made to receive a business receipt, with a 10-second pause between each attempt.

2022.2 HF03

ALM31/221523: Extended submission: The process owner cannot edit approvers and documents in the Submission rejected task

If an approver rejects a task, the process owner cannot add or remove approvers and documents in the Submission rejected task/smartmail. The Edit buttons were not shown in the Submission rejected task/smartmail.

Corrected

ALM10/218041: Hearing: Documents are not available in the hearing summary

When all actors in a hearing process have responded to a hearing and the process owner receives the

summary task/smartmail, the process owner cannot open the attached documents from the summary task/smartmail.

Corrected.

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

When accepting a mass dispatch after three attempts to validate the recipient list, the documents in the mass dispatch were not included shown in the history document.

Corrected.

219442: Mass dispatch: Deleting generated letters fails with an Oracle error

When recycling and deleting a letter (PDF document) and the corresponding history document, WorkZone shows an Oracle error message, and the letter and history document were not deleted.

Now, the message and history documents are deleted, and no error message is shown.

219411: Mass dispatch: Generated letters are locked by SJPROCESSUSER write access after the process was cancelled

After cancelling a Mass dispatch process, the generated letters were locked by SJPROCESSUSER write access.

Corrected.

219371: Mass dispatch: Missing space before the error description in the Mass dispatch failed task

A blank space was missing between the message and the error description in the Mass dispatch failed task/smartmail.

Corrected.

Improved NgDP receipt handling

Search in the NgDP EventLog has been improved.

2022.2 HF04

222468: Stabilization of the workflow host

In some situations, aborted process workflows terminated the application pool process (w3wp.exe).

Corrected.

REM 829105/222159: Process owners cannot close processes

Process owners could not close processes, and therefore the processes could not be completed after approval. When a process reached the process owner for approval, and the process owner clicked Approve in the approval task, the error message "The task has been completed or is out of date" was shown.

The issue only occurred in rare cases in environments with multiple databases where wf_id in the different databases referred to different active workflows or the form_id in the databases was different.

The issue was caused by the caching mechanism in workflows, and it only occurred on web servers that serviced multiple databases.

Corrected.

REM838860/226571: In some situations processes stop due to an error in Microsoft OData 5.8.5

Microsoft OData has been downgraded to version 5.8.4 to solve this issue.

226317: Mailbox monitor: Login credentials are shown in the workflow log when logging is activated

When querying the workflow log using WorkZoneQuery builder, the workflow log exposes the login credentials of the Exchange user who has access to the monitored mailbox.

To fix this issue, you can turn off logging or install this hotfix. Installation of the hotfix ensures the login credentials are not shown in the workflow log.

 

2022.2 HF01

2022.2 HF02