Released hotfixes for WorkZone 2021.3

2021.3 HF01

This hotfix updates the WorkZone Configurator with the new Use document culture for date format fields setting in WorkZone Configurator (Configurator > PDF > Engine configuration > For Word documents). See the description for WorkZone PDF Hotfix 03 below.

2021.3 HF01

Performance loss experienced after upgrading to WorkZone 2021.3

TFS number: 198233

INC4306828 QB

INC4305398

A noticeable performance loss was experienced when conducting database operations after having upgraded to WorkZone 2021.3. The auto performance Oracle hint feature of OData queries was broken, leading to longer query times for certain complex queries on entities such as File and Record. The issue has been fixed and the Oracle hints can now be applied to the relevant queries again.

2021.3 HF02

Inaccurate PDF rendition of updated documents

TFS number: 203194

CS1431425

The Valid marking of a pdf rendition of a document could erroneously be set to True when the original document was updated within the same second as the PDF rendition was generated. This resulted in the PDF document not accurately reflecting the changes in the original document and because the Valid marking was set to True, a new PDF rendition of the document would not be performed.

This has been fixed.

2021.3 HF01

PDF: SmartPost history report contains wrong date in header

TFS Number: 200779

INC4232619

INC423256

In the SmartPost History document for a SmartPost task that was started and completed on the same day, the date in the header of the history document was incorrect. Now, the date in the header of the SmartPost history document will correctly reflect the SmartPost dates.

2021.3 HF02

This hotfix was withdrawn before being released.

2021.3 HF03

PDF: Multiple language date format settings in PDF not working

TFS Number: 203126

INC3819171

When converting the Word documents containing multiple languages to PDF, the date format fields (that is, {Date}: placeholder tokens) were always using the date format for a language, specified for WorkZone in WorkZone Configurator. Now, by enabling the new Use document culture for date format fields setting in WorkZone Configurator (Configurator > PDF > Engine configuration > For Word documents), you can ensure that the date format fields will follow the source culture of a relevant page.

2021.3 HF01

Assign Read rights to WzpSVCapp pool and process user windows account

After installing the hotfix, you must assign Read certificate rights to the Windows account used by the WorkZone user as well as to the IIS APPPOOL\WzpSvc app pool on all Web servers as well as the Agent server.

For information about installation and configuration of the NgDP integration, please see:

Configure SmartPost to use next generation Digital Post (NgDP)

Install and configure WorkZone e-Boks Push Service

Process dispatchers

e-boks materials

e-Boks mailbox mapping

 

If you need help with the implementation of the NgDP integration, KMD WorkZone Consulting offers NgDP relevant services.

Please contact your Service Delivery Manager for more information.

Assign Read rights to WzpSVCapp pool and process user windows account

After installing the hotfix, you must assign Read certificate rights to the Windows account used by the WorkZone user as well as to the IIS APPPOOL\WzpSvc app pool on all Web servers as well as the Agent server.

Known issues and workarounds

Processes will not start after installing the hotfix

If you can't start processes after installing the hotfix:

do AppPoolRecycle for "WzpSvc" and "EBoksPushAppPool" on all WorkZone servers, if you still can't start processes, run the IISreset command on all WorkZone servers.

General WorkZone Mass Dispatch errors

The WorkZone Mass Dispatch feature may contain errors that may impact core or peripheral functionality of WorkZone Mass Dispatch.

These errors have not been satisfactorily identified or classified at the time of the hotfix release.

CPR/CVR message reception

CPR messages from the Danish Digitization Agency are received and placed in WorkZone correctly but CVR messages are not received.

 

2021.3 HF02

Asynchronous receipts result in a “SmartPost was unsuccessful” message

TFS Number: 200930

Asynchronous receipts resulted in a “SmartPost was unsuccessful” message after 5 minutes. Now receipts are retrieved after the message has been sent and the number of retries and delay is controlled from wzp_error_manager. You can set how many times, SmartPost should try to receive the business receipt and at what interval in the error manager. Default is 180 times with an interval of 900 seconds.

Mass Dispatch: Error checking e-Boks subscription status of CVR recipients

TFS Number: 200589

If a mass dispatch message was sent to a CVR company as the recipient, an error message saying that the company was not subscribed to e-Boks was received. Sending a standard SmartPost message to the same CVR company via NgDP resulted in a successful dispatch. The issue was caused by an error in the procedure that checks for subscription status of CVR recipients.

The procedure now checks the correct field in the reply from NgDP.

IDs in the SmartPost history documents have changed

The IDs that are shown in the SmartPost history documents have been changed to show IDs that can be used to search for errors in NgDP.

Known issues and workarounds

Broken dispatcher sequences after upgrade

If you have multiple dispatchers of the same type, for example dispatchers of the e-Boks type, that are set up for either e-Boks or NgDP, the dispatch sequences will break after upgrade. The dispatch sequences will fall back to the first dispatcher that it finds after the upgrade. Note that this also applies to the dispatcher that is used by the e-Boks Message Handler service workflow, which is used to retrieve messages from e-Boks or NgDP.

To work around this issue, you should verify the dispatch sequences after the upgrade and correct them if needed. Before you do the upgrade, make sure to document how the dispatch sequences are configured, for example by taking a screenshot.

Endless error messages on the agent server

TFS Number: 200930

If you have configured an NgDP dispatcher incorrectly with an invalid system ID, corrected it, and recycled the app pool, you will see a large number of errors on the agent server because of an invalid system ID in the PushServiceSystemConfiguration.

To fix this issue, you must load the system configuration using this command:

Get-PushServiceSystemConfiguration

and then delete the incorrect system configuration for the specific system using this command:

Delete-PushServiceSystemConfiguration -SystemId <systemid>

After removing the incorrect system ID, the logging will stop.

Process labels are shown in German

If process labels are shown in German, follow the steps below to solve the issue.

1. Enable German in WorkZone Configurator. Go to Global > Language settings.
2. Recycle the sjvc app pool, or perform the iisreset command on the server where the process packages are loaded.
3. In ScanSql or SQL Plus, run:

update wzp_package set md5hash = '' where name in ('Basis','Agency','Extended','ExternalCommunication','F2','Interact','MassDispatch','Ministerial')

4. Run the Process configuration again:

'C:\Program Files (x86)\KMD\WorkZone\Process\Bin\Scanjour.Process.Configurator.exe -ForcePackageLoad'

The first time, the configuration will fail just before it gets to the loading of the process packages, and you need to run step 4 one more time.

5. Disable German in WorkZone Configurator. Go to Global > Language settings.
6. Recycle the sjsvc app pool, or perform the iisreset command again on the server where the process packages are loaded.