Frigivne hotfixes for WorkZone 2024.0

249354: Users with global access cannot update permissions for authority-protected documents and cases

Users with global access (* access code) cannot change the access code (both read and write) for cases and documents, if their "License" property belongs to a different authority than that user's authority.

Corrected: Users with global access (* access code) can change access codes on both cases and documents, even if their license belongs to an authority different from user's own.

251209: Adding Case Icon condition with FileClass_Value breaks editing of AGM items

Corrected.

252340: 'IsInheritable' flag is missing in WorkZone Client configuration

After creating a WorkZone Client configuration with inheritance to subunits, the 'IsInheritable' setting is not included into the exported .json configuration file.

Corrected.

252341: Cannot find unit configuration with inheritance when exporting a WorkZone Client configuration

When exporting WorkZone Client configurations, there is no indication of inheritance in the configuration names, meaning that you cannot tell apart the configurations with and without inheritance.

Corrected.

246964: Flagging/Unflagging resulting in an error

Flagging/unflagging items randomly fails with the message "An error occurred while flagging/unflagging this item. Please contact your system administrator to resolve the issue".

Corrected.

252636: Flagging not working when items are not part of user's MRU

Flagging functionality does not work if flagged items are not part of the user's most recently used (MRU) items.

Corrected.

246170 Error in CPR integration

Some actions were executed twice.

Corrected.

246172: In Oracle, job_queue_processes must be greater or equal to 15

Corrected.

246173: The job that sets the current address for a file party does not set the primary party's address

Corrected.

ScanSQL issues

The following ScanSQL bugs have been fixed:

245697: It is not possible to view settings for the individual freetext indexes in ScanSQL.

246188: ScanSQL crashes when clicking Preferences in Text indexes.

246189: ScanSQL crashes when clicking Object problems.

246190: ScanSQL crashed when cancelling Get file by doc_id.

246637: ScanSQL error, job setting the current address, Wait longer for synonym's job to start.

248097: Hard deletion of documents uses a wrong datetime stamp when stamping Updated/UpdateTime on the file

Corrected.

248156: Database - sjpk_sja_pkb update_time, updated and update_user are not set on SJ_STD cases

The AD replicator did not set update time om standard cases.

Corrected.

246391: SOM orderby CustomProperty_Summary uses inner join

Search results can be wrong when ordering by _Summary part of a custom property when it is of the type droplist.

Corrected.

248638/CS0001799: Address updates lack end dates

When updating more than one address from the CPR register at the same time, there were cases where an end date was not set.

Corrected.

251881: Incorrect update of default addresses

If either the Change case party address on open cases to the contact's default address feature setting or the Change case party address on open cases to the contact's default address if the previous address is inactive feature setting is enabled in WorkZone Configurator, the change of address on case parties and on the primary party on cases did not work as intended. Furthermore, the changes were not logged and shown on the Life cycle and the Contact reference history tabs on the case detail page.

Corrected.

See also:

Configure the behavior for selection of default addresses

The Detail tabs

253330: Select Custom Properties as collections

The feature "OData > Select Custom Properties as collections" that was introduced in WorkZone 2024.2 is now available in WorkZone 2024.0.

INC0010502/ INC0010674: CPR Batch does not update existing citizen

The primary party (citizen) on a case was not updated correctly with the citizen’s address.

Corrected.

252700/I252700/NC0010497: Documents in hierarchy tab did not work

An error occurred when opening the Documents in hierarchy tab in WorkZone Client, when there were circular references between documents.

Corrected.

252673/CS0001983: Inconsistency in the File/UserKey field

When searching in the FileContacts entity in WorkZone QueryBuilder, the query result returned inconsistent File/UserKey values.

Corrected.

253325: CPR Batch required a specific entry in the source_record field but CPR Online does not support it

If a CPR number existed in the name field but not in source_record field, then CPR Batch required a special entry in the source_record field but CPR Online did not support it.

CPR Integration, CPR Online and CPR Batch

Contacts who are created with the name type C without using WorkZone CPR Online can now be updated both via CPR Online and via CPR Batch. However, if you use CPR Batch, it requires that the contact is subscribed to CPR in a different way than through WorkZone CPR Online.

Before this hotfix, you had to create a specific entry in the source_record (save_type = ’X’) for this to work, and then it only worked for CPR Batch, not for WorkZone CPR Online.

If you have created specific entries in source_record (save_type = ’X’), you must remove them.

A new parameter is now available in CPR Batch:

/exists The name is only imported if the name is already registered in WorkZone's name register name type C.

The purpose of this hotfix is to update the PDFTron licencing key in the mobile app.

Fixed issues with the rank re-order functionality for tasks.

250687: Unhandled exception, after which duplicate contacts and duplicate mail documents are created in WorkZone

Some users have reported encountering duplicate emails and contacts when saving from WorkZone for Office. The root cause of this issue was identified as double-clicking on the Save button.

Corrected: This problem has been resolved, and users should no longer experience it.

250656: Add type 'Unique' as a merge field

Contact custom type Unique can be used as a content control now.

252588: (Office 2019/2021): When mail conversation includes recall message requests, users cannot save any mail from that conversation on a case

If email conversation includes recall message requests, users cannot save any mails from that email conversation on a case.

Corrected.

253761: Occasional errors "This file cannot be saved because it is read-only" after starting a process

CS0001974

When enabling editing for a read-only (archived or locked) WorkZone document via Word/Excel/PowerPoint, and then starting a process, WorkZone for Office sometimes shows an error that this file cannot be saved because it is read-only.

Corrected.

INC5135489/238854: Links in PDF/UA documents fail

Links did not work when documents were converted to PDF/UA format.

Corrected.

INC5270681/241658: The WorkZone PDF Crawler admin USER is shown in the Updated by field

After upgrade, the WorkZone PDF Crawler admin user was shown in the Updated by field on cases instead of regular users.

Corrected.

237514: Significant increase of the size of PDF documents when sent as attachments in a SmartPost process

The file size of some PDF documents increased significantly when they were sent as attachments in a SmartPost process.

The size of SmartPost letters with attachments has been reduced.

Please note that this correction requires WorkZone Process hotfix 1.

222508/CS1473851/INC4145553: Failed PDF documents (ModDate)

Some PDF documents could not be generated due to an issue with ModDate.

Corrected.

246423: Documents are downloaded instead opening in the preview pane

PDF documents were downloaded instead of opening in the preview pane.

Corrected. When a PDF rendition is requested, the browser no longer download it as a file.

242599: SmartPost fails on unexpected character when PDF/UA is enabled (Exchange dispatcher)

The SmartPost process failed when using the Exchange dispatcher. The error was caused by an unexpected character when PDF/UA was enabled.

Corrected.

241537: PDF Crawler does not reconnect or fail

The check of the connection status has been improved, and now the container readiness probe returns unhealthy when PDF Crawler cannot access OData.

PDF Crawler performance improvements

The following bugs have been fixed as part of performance improvements of the PDF Crawler service:

• 237622/ CS1990190/ INC5072540: PDF documents are not generated automatically from Word documents

• 246234/CS2188718/ INC5409546: PDF Crawler is slow

• 235313: PDF Crawler performance issue

248521/INC0010203: Missing information on case printouts

Dates and case parties were missing on case printouts.

Corrected

249548: WZPDF Error when generating PDF documents

A PDF conversion error occurred due to 'incorrect namespaceUri'.

Corrected.

248988: PDF/UA validation failing on environment without internet connection

PDF/UA validation failed on environments without internet connection.

Corrected.

249855/CS0002139: PDF/UA validated documents could not be edited

It was not possible to edit a PDF/UA validated document, for example move or copy pages in the PDF document.

Corrected

253536/INC0010756: WorkZone PDF Crawler performance issues

To improve performance, the way that PDF Crawler selects files for rendition has been enhanced. Moreover, we have changed the recommended settings for the RecordsLimit, SuspendInterval, and WorkerCount parameters. The default settings are:

• RecordsLimit: 50

• SuspendInterval: 00:00:30 (30 sec)

• WorkerCount: 2

Note that you need to set the values manually when upgrading to this hotfix.

For more information about the parameters and how you can optimize performance, see Configure WorkZone PDF Crawler.

253304/INC0010494: SmartPost fails

WorkZone PDF Engine had synchronization issues with WorkZone PDF Crawler.

Corrected.

245629/CS2072931: The process owner did not receive a PDF/UA validation failed task/smartmail

When sending a SmartPost message with documents that failed the PDF/UA validation, the process owner did not receive a PDF/UA validation failed task/smartmail.

Corrected.

All 2024.1 WorkZone Process updates are included in the 2024.0 hotfix 1.

New features

SmartPost performance improvement

Sometimes the NgDP response times became slow when checking for NgDP receipts in the NgDP service. This is done through the NgDP service Event Log and in the receipts to ensure all receipts are received. This look-up affected other processes. The issue has been fixed in the NgDP dispatcher.

Bug fixes

237514: Significant increase of the size of PDF documents when sent as attachments in a SmartPost process

The file size of PDF documents increased significantly when they were sent as attachments in a SmartPost process.

The size of SmartPost letters with attachments has been reduced.

245743: WZP webservice: The date format in the user tasks was not aligned with the selected language culture in the clients

When a user with one culture set, for example Danish, created a process through the WZP API, the date format in the user tasks when opened from a client was sometimes not aligned with the selected culture in the client, for example WorkZone Client.

Now, the dates are shown in the culture that the user has selected on the client.

247891: Advanced submissions: Steps were broken after editing a process

An error occurred when approving advanced processes that that had been edited. The states of the steps in the process were broken.

The states of the steps are now same as before editing the process.

INC5294029/CS2110012/242636: Inconsistent replies from NgDP as to whether a contact is subscribed to Digital Post

Inconsistent replies from NgDP as to whether a contact is subscribing to Digital Post or not is resolved by recognizing replies with no error and no reply as no subscription to digital postal. The issue has occurred for contacts with CPR who live abroad.

Corrected

245695: New subscription status Closed NgDP

NgDP has introduced a new Closed status for contacts’ mailboxes. WorkZone handled this status as if the contact was not subscribed to Digital Post.

Corrected

CS0001759: SmartPost issues

Release 66 from Digitaliseringsstyrelsen reintroduced an EventTag that broke the backward compatibility of WorkZone. As a result, receipts were delivered and received incorrectly in WorkZone, and customers could experience that SmartPost processes failed with the error "Dispatcher NgDP PROD failed with error: e-Boks error. Server error 1999: Error getting Contact response TooManyRequests 429 Too Many Requests". The error was shown in the workflow log.

Corrected.

246004: Asynchronous sync of NgDP receipts

There was an issue with asynchronous synchronization of NgDP receipts.

The issue has been corrected to make sure that long NgDP response times do not drain the application pool.

Known issues

New NgDP dispatchers have the same names as old e-Boks dispatchers

After upgrade, new NgDP dispatchers are created instead of the new versions e-Boks dispatchers. The names of the old e-Boks dispatcher and the new NgDP dispatchers are identical, which makes it difficult to see which dispatcher is used by the e-Boks message handler service workflow.

To work around this issue, you can set an end date on the dispatcher that you do not want to use and make sure that the e-Boks message handler service workflow points to the dispatcher without end date.

SmartPost messages are not sent to copy recipient (same as recipient)

After upgrade, messages are not sent to the copy recipient if the copy recipient is the same as the recipient.

New feature

SmartPost Extended logging

You can now enable extended logging by turning on a new DebugOutput setting in the NgDP dispatcher in WorkZone Configurator. If you turn on this setting, all requests to the NgDP service will be written to the workflow log. You should only turn on this setting if you are investigating errors from Digitalieringsstyrelsen's NgDP service.

By default the setting is turned off.

Bug fixes

The SmartPost history documents do not show the external ID

When a SmartPost message failed, the External Id field in the history was empty.

Now, the history document shows the MessageUUID of the sent message in Eksternal Id field.

253359: Performance issue with case activities when using the UpdateEntity activity effect

Customers who have defined a considerable number of custom properties experienced reduced performance when using the UpdateEntity activity effect.

The performance was reduced if OData requests do not have projections. If, for example, you want to use an OData request to read the case number and the OData request doesn't have a projection, all information about the case is retrieved, not only the case number, which affected performance. Now, all OData requests have projections.

251546: SmartPost fails when sending attachments as separate documents

SmartPost fails when sending a SmartPost message with attachments and selecting the Send attachments as separate documents (only e-Boks/NgDP/Exchange) checkbox in the Send SmartPost dialog.

Corrected

253027: Parallel service workflows are only running in parallel for 29 hours

When running a parallel service workflow, for example the Case monitoring service workflow, in an environment with multiple agent servers, the service workflow only ran on one server after 29 hours.

Corrected

New feature

Mass dispatch supports the NgDP dispatcher

Mass dispatch now supports use of the NgDP dispatcher. As of the 2024.0 release, you must use the NgDP dispatcher instead of the e-Boks dispatcher.

Skipped.

WorkZone Mass Dispatch Hotfix 3 is required because the functionality of WorkZone Process and WorkZone Mass Dispatch are interconnected.