Released hotfixes

216760 Upgrade of WorkZone Client configurations with saved searches failed

When upgrading to WorkZone 2022.3, WorkZone Client configurations with saved searches did not upgrade due to missing quotation marks around the GUIDs that identify saved searches. This has been fixed.

218233: 'sj_arkiv' user does not handle a password change

The archive drive does not manage a password change of the user 'sj_arkiv'.

Corrected.

INC470075/216822: Landing page returns a forbidden error after upgrading from 2021.1 to 2022.3 HF01

After upgrading WorkZone from 2021.1 to 2022.3 HF01, the WorkZone Client landing page returns a forbidden error (the web.config file is not updated automatically).

Corrected.

217986: OAuth2 issue on cloud environments caused by TLS 1.1

It was impossible to log in to WorkZone on cloud environments with TLS 1.1 (Scanjour.Services.OAuth2 errors).

Corrected.

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

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

The upgrade time has now been reduced significantly.

Not published

246170: Error in CPR integration

Some actions were executed twice.

Corrected.

Case group filtering during case creation

TFS number: 216489

When creating cases in WorkZone for Office, you will now only be able to see and select case groups that are allowed to be used for case creation (that is, where Case creation and Selectable options are enabled in WorkZone Configurator > Taxonomy > Classification scheme > Create case group by your administrator). Case groups set up as non-selectable or not used for case creation in WorkZone Configurator will not appear in the Case Group field.

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.

Interact connector service workflow - Performance optimizations

TFS number: 238484

The 30 seconds delay between handling forms has been reduced from 30 seconds to 1 second.

In some situations, processes stop due to an error in Microsoft OData 5.8.5

TFS number: 226571

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

Out-of-memory issues

TFS number: 238801

The Process application pool (WzpSvc) now runs 64 bits, which reduces the possibility of out-of-memory issues with workflows and case activities.

Not published.

240353: Corrections in Hotfix 4

The following issues have been fixed in this hotfix.

Service workflows started multiple instances

There was an issue with service workflows starting multiple instances because they kept the status 'Running' for too long.

Now, the service workflows update a field in the database that prevents the service process agent from starting a new instance.

When the Application Pool is recycled, running processes may be restarted

When the Application Pool is recycled, running processes may be restarted, which sometimes resulted in SmartPost sending a message twice.

Now, when the Application Pool is recycled, it will try to wait for processes to finish before starting the new Application Pool.

Performance issues with the Case monitoring and Interact connector service workflows

To improve performance, you need to manually to update the hostnames in WZP_SERVICE table by using SQL.

Performances issue with the Interact connector service and Case monitor workflows

Performance issues were seen when, for example, the Interact connector service workflow handled Interact data, or the Case monitor service workflow processed cases.

Now, the Interact connector and Case monitor service workflows have a new FetchInterval parameter that you can use to set the interval at which the service workflow fetches and processes Interact data, cases, or case activities. You can, for example, reduce the speed of the Case monitor service workflow to allow that case activities will be created every minute instead of every second, which is the default value.

FetchInterval (Interact connector)

The interval in seconds between fetching and processing interact data. The minimum interval is one second.

FetchInterval (Case monitor)

The interval in seconds between fetching and processing cases. The minimum interval is one second.

Content controls fail in SmartPost

Sometimes the merge of content controls failed in SmartPost messages.

Now SmartPost tries to send the message once more (Retry) when the merge of content controls fails.

An Interact connector error case was sometimes created when there were no errors

Corrected.

SmartPost does not retry sending message when getting receipts failed

Corrected.

The Case monitor service workflow was searching for all new cases

The Case monitoring service workflow was searching for all new cases instead of the new cases that matched the rule.

Corrected.

Overlapping parallel service workflows

When the service process agent registered that a service workflow was in the state 'Running' but it did not run. The agent tried to stop the service workflow, but this was not possible for a running process. Now, this is possible but only when the process host and the service process agent run on the same machine.

Multiple instances of the same case activity on the same case

Sometimes multiple instances of the same case activity were started on the same case when using the Case monitor service workflow.

Now, WorkZone checks if there is already an active process of the same type on the case.

Processing cases and forms from Interact multiple times

If service workflows were started more than once, it sometimes resulted in processing cases or forms from Interact multiple times.

Corrected.

New NgDP event type in the event log

NgDP had made a new type of invent in their event log.

SmartPost now supports it.

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

Inconsistent reply 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 been has occurred for contacts with CPR who live abroad.

245695: New subscription status Closed NgDP

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