=============================================================================== Release Information =============================================================================== KMD WorkZone Process 2021.1 Hotfix 6 build No. 21.1.22039.14891 Released February, 2022. =============================================================================== Client Prerequisites =============================================================================== You must upgrade WorkZone for Office to version 2021.1. You must upgrade WorkZone Client to version 2021.1. Supported client OS: Refer to the WorkZone for Office Support Matrix (see the WorkZone for Office Administrator Guide). =============================================================================== Server Prerequisites =============================================================================== - Microsoft Windows Server as defined for WorkZone Content Server 2020.1. - Exchange Server 2016 and 2019. - Exchange Online - Server module: KMD WorkZone for Office 2021.1 KMD WorkZone Content Server 2021.1 KMD WorkZone PDF 2021.1 KMD WorkZone Configurator 2021.1 =============================================================================== Installation =============================================================================== Overview -------- KMD WorkZone Process 2021.1 Hotfix 6 consists of the KMD WorkZone Process.msi server package. =============================================================================== Documentation =============================================================================== The documentation for this release is: Release overview and documentation is available on the WorkZone Documentation portal. https://docs.workzone.kmd.net/2021_1/da-dk/ https://docs.workzone.kmd.net/2021_1/en-us/ Readme (this document). ============================================================================== Bugs fixed in this hotfix ============================================================================== 200930: Asynchronous receipts result in a “SmartPost was unsuccessful” message ------------------------------------------------------------------------------ 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. Note: There is no user interface for configuration of timeout and interval. This is a customization. The configuration will be lost after reinstallation. 200589: Mass Dispatch: Error checking e-Boks subscription status of CVR recipients ---------------------------------------------------------------------------------- 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. ============================================================================== New features introduced in this hotfix ============================================================================== 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. 200930: Endless error messages on the agent server -------------------------------------------------- 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 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.