Released hotfixes for WorkZone 2023.0

235092: Adding the FileClass_Value condition to File icon breaks editing of meeting agenda Items

Editing meeting agenda items in WorkZone Client becomes impossible after adding the FileClass_Value condition to a File icon in WorkZone Configurator.

Corrected.

WorkZone Client: When adding data to a detail page, screen focus moves up

TFS: 239286, CS1909619, INC4928202

When adding data to a case or a document's detail page, the focus moves to the top of the screen, instead of staying on the field where the data is being added.

Corrected.

WorkZone Client: Using unicode filenames from Templafy fails

TFS: 241750

Creating documents from Templafy fails, if Templafy template contains unicode characters in its name.

Corrected.

WorkZone Client: Document search errors

TFS: 228619, CS1876048, INC4891414

When searching for documents with created date filter, an error appears that "A binary operator with incompatible types was detected".

Corrected.

WorkZone Client: Process list fails to open cases

TFS: 251320

Corrected.

221181: Long upgrade times when upgrading from WorkZone 2022.3 and earlier releases

Long upgrade times were experienced when upgrading WorkZone 2022.3 or earlier releases.

The upgrade time has now been reduced significantly.

221190: Database upgrade fails in WorkZone Cloud Edition

There was an issue with concatenation of varchar2 and clob in the Oracle cloud database.

Corrected.

227089: OData: Expanding multiple custom lists fails

Expanding multiple custom lists may fail.

Corrected.

Improvements for working with WorkZone meetings

• Meeting attendees can now create WorkZone meetings. Previously, only meeting organizers could create WorkZone meetings.
• Users can open a WorkZone meeting case in WorkZone Client directly from the WorkZone pane.
• If multiple WorkZone meetings exist for the same Outlook meeting (for example, if several participants have created parallel WorkZone meetings due to access restrictions to an already existing meeting case), they will be listed under the new Case droplist on the WorkZone pane, so users can select the needed meeting case.

Case groups are not retrieved from WorkZone during case creation in Outlook

TFS number: 222278

When creating a new WorkZone case using the WorkZone for Office add-in in Microsoft Outlook/Word/Excel/PowerPoint, the 'Case group' selection popup is not loading, causing the Outlook to freeze.

Corrected.

Child case group is cleared during case creation in Outlook

TFS number: 222365

When trying to save a new WorkZone case with the selected child case group using the WorkZone for Office add-in in Microsoft Outlook/Word/Excel/PowerPoint, the selected value is reset, making it impossible to create a case with the required child case group.

Corrected.

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

WorkZone Meeting support for shared mailboxes

This release enables using old WorkZone Meeting add-in with WorkZone for Office, including support for shared mailboxes (which is currently not possible with the new WorkZone Meeting add-in in WorkZone 365).

Installation and setup notes:

1. After completing the server-side installation, update the deployment config.xml file as folows:
   • Add for the Server: <WZMServer Install="True" Version="2023.0 RC" />
   • Add for the Client: <WZMClient Install="True" Version="2023.0 RC" Url="https://db01.lmdom.local/" />
2. After deployment, execute the InsertMeetingIntoVersions.sql file. It needs to be installed on the same server as OData, because this add-in server component is adding a custom OData endpoint definition. If you use Olympus, you can do it like this:
<PostConfigs>
<Invoke-Command Scriptblock="sqlplus sjsysadm/sjsysadm@db01 &quot;@C:\Install\InsertMeetingIntoVersions.sql&quot;" />
<!-- .... -->
<PostConfigs>
3. After deployment, perform IISRESET on all servers where you have installed this component.

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.

222523: Wrong time stamp in SmartPost history documents

An earlier hotfix that was related to setting the local time zone in the SmartPost history documents (PDF) was removed to support WorkZone - Cloud Edition. The removal of this hotfix resulted in wrong time stamps in the history documents on WorkZone on-premises.

To solve the date issue in both WorkZone on-premises and WorkZone Cloud Edition, you can now configure the time zone to local time or UTC time. The default time zone is the local time, which is the time of the local server.

When the SmartPost history documents are generated, the dates in UTC format are converted to the configured time zone. Both the local time and the time zone offset to UTC will be shown in the history document, for example, 17-11-2022 12:15:00 +01:00. Date only fields are displayed in the configured time format but only the date is shown. When no time zone is configured or the configured time zone cannot be applied, the default time zone is the local time zone.

You configure the time zone by using a new WorkZone PDF Engine and WorkZone PDF Crawler configuration parameter that sets the time zone. If the configuration is left empty, the default time is the local time zone. You can set the parameter in the deployment configuration as CustomParameter to DBConfig, or in the command line installation by setting these parameters:

-EngineParams:"TimeZoneId=Europe/Copenhagen"

-CrawlerParams:"TimeZoneId=Europe/Copenhagen"

If you want to change the TimeZoneId later, you can update it directly in the database:

update WZPDF_CONFIGURATION set Custom_value='Europe/Copenhagen' where Target='PDFENGINE' and Name='TimeZoneId';

update WZPDF_CONFIGURATION set Custom_value='Europe/Copenhagen' where Target='PDFCRAWLER' and Name='TimeZoneId';

Please refer to the Microsoft article Default Time Zones for supported time zone standards and to List of tz database time zones in Wikipedia for IANA (Internet Assigned Numbers Authority) time zone names.

241110: License watermark appears in PDF versions of emails in WorkZone

CS2011026, INC5107306

A license watermark with an external link appears on PDF versions of all emails.

Corrected. The license sometimes was not loaded correctly due to concurrent threads. To resolve this, the lock has been implemented, so that threads wait for their turn to access the license, which will prevent the license watermark from appearing.

INC5193825/240302: Error when using the Public access, printout of the case documents template to print case documents

An error occurred when printing case documents using the Public access, printout of the case documents (Aktindsigt, udskrift af sagens rapporter) template if there were more than 250 custom fields on a record.

Corrected. The OData query for filling in the values in the Public access, printout of the case documents report has been corrected.

222508/INC4145553: Failed PDF documents (ModDate)

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

Corrected.

248521/INC0010203: Dates and case parties were missing on case printouts

Dates and case parties were missing on case printouts.

Corrected.

Support for multitenant installation

This hotfix supports installation of WorkZone Process in a multitenant environment. A new Customer parameter has been added to WorkZone Process Configurator than allows you to configure WorkZone Process for a specific customer in a multitentant environment. For more information, see Multitenant installation.

222468: Stabilization of the workflow host

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

Corrected.

INC4893877/226317: Mailbox monitor: Login credentials are shown in the workflow log when logging is enabled

When querying the workflow log using WorkZone QueryBuilder, 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.

228304: SmartPost and Mass dispatch: Duplicates of received messages are saved in WorkZone

In rare cases, when WorkZone receives messages from NgDP, the messages are saved multiple times on the WorkZone case if there is a considerable number of incoming messages in the NgDP queue.

Corrected

226694: Mass dispatch processes fail if multiple contacts refer to the same case

Mass dispatch processes fail if more than 50 contacts are mapped to the same case in the recipient list.

Corrected

219475: Mass dispatch processes fail due to time-out

Mass dispatch processes fail due to time-out when adding case or document party relations.

Corrected

New feature

Mass dispatch: Save sent messages to an existing case if no case is specified in the recipient list

You can now save sent letters on a default case if there are no cases mapped to recipients in the Case sheet in the recipient list.

In the Start mass dispatch dialog, go to the Recipient cases tab, and then select the Save sent messages on an existing case check box and select a case.

See Start a mass dispatch (step 14) and Save letters on an existing case in the WorkZone Mass Dispatch User Guide.

INC5027242/229501: SmartPost - Merge content controls issue

Letter date content controls were merged into other types of content controls if these content controls contained xml-mappings and were inserted immediately after a Letter date content control in the letter document.

Corrected.

New push notification certificate for WorkZone Mobile

A new certificate used for sending push notifications from WorkZone Process to WorkZone Mobile is now available. To use this certificate, you need to change the Scanjour.Process.Notification.AgentHost.exe.config file. See Configure push notification certificates for WorkZone Mobile.

237801: Process workflows fail after upgrade

Several process workflows failed after upgrade from 21.1 hotfix 7 or 8.

Corrected

This hotfix also includes bug fixes related to upgrading running workflows.

238258: Errors when taking ownership of SmartPost processes

Errors occur when users try to take ownership of SmartPost processes.

Corrected.

237935: Searching for contacts fails in the Submission (Extended) process

When users try to forward a submission task by using the Forward button, the search for the contact to forward to fails when the there is a large number of contacts.

Now, the search works when opening the Approve Submission task from WorkZone Client and clicking the Forward button.

Known issue

The search does not work when opening the Approve Submission task from Outlook when there is a large number of contacts on the list.

240275: Mass Dispatch – An error occurs if the recipient list contains recipients that are not registered for digital post

If the recipient list contained contacts that were not registered for digital mail, an error occurred “Error during process run”. The dispatch appeared as successful, but the letters were not sent.

Now, the dispatch of the letters will continue to the validated recipients that are registered for digital mail.

241579: Mass Dispatch – An error occurs if the recipient list contains contacts with the same value in the "TaxIdNo" field

If the recipient list contains contacts that point to the same main number, for example in the case where there is one main CVR number in TaxIdNo field for multiple production unit numbers, an error occurred when sending the letters.

Corrected.

239625: Extended/Advanced Submission: Reject to and Conditional do not work for units

Units were not shown in the list of approvers when clicking Reject to or Conditional in a task.

Corrected.

239044: Flexible mapping of Interact form data to WorkZone data

The Interact connector service workflow now supports that you can create field mappings by using a custom XSLT transformation. You can create more advanced mappings in a custom XML format compared to what the WorkZone Interact add-in offers. You can, for example, handle multiple contacts, contact roles, and that a contact has more than one address. An XSLT transformation is required for the Interact connector service workflow to retrieve Interact data from a custom XML format.

For more information, please refer to the 2024.0 documentation:

Create and configure an Interact connector service workflow

Field mapping in Interact forms to WorkZone data

Sample XSLT transformation and XSD schema

238215: Limitation on number of letters that can be saved on existing cases

The mass dispatch stops when reaching a limitation of 100 letters that can be saved on existing cases.

Corrected.