=============================================================================== Release Information =============================================================================== KMD WorkZone Mass Dispatch 2020.3 Hotfix K2E build No. 20.3.22019.05 Released February, 2022. =============================================================================== Client Prerequisites =============================================================================== You must upgrade WorkZone for Office to version 2020.3. You must upgrade WorkZone Client to version 2020.3. 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.3. - Exchange Server 2013 and 2016. - Exchange Online - Server module: KMD WorkZone for Office 2020.3 KMD WorkZone Content Server 2020.3 KMD WorkZone PDF 2020.3 KMD WorkZone Configurator 2020.3 =============================================================================== Installation =============================================================================== Overview -------- KMD WorkZone Mass Dispatch 2020.3 Hotfix HFK2C consists of the KMD.WorkZone.MassDispatch.Setup.msi server package. =============================================================================== Documentation =============================================================================== The documentation for this release is: Release overview and documentation is available on http://workzonesupport.kmd.dk/support/dokumentation-workzone-mass-dispatch/. Readme (this document) and WorkZone Mass Dispatch User Guide. ============================================================================== Bugs fixed in this release ============================================================================== 200106/ALM-98: Mass Dispatch uses the access code for case handler and not the current user ------------------------------------------------------------------------------------------- Mass Dispatch used the access code of the case handler on the case and not the access code of the current user. The core issue was that the MASSDISPATCHSEND access code was not verified, and users without the MASSDISPATCHSEND access code were allowed to approve the dispatch. Correction The validation user task is no longer sent to the case handler when the Send to case handler for approval/Send til sagsbehandler til godkendelse check box is selected. It is only the approval user task that is handled by the case handler in this case. 200589/ALM-125: Validation of CVR number for the e-Boks subscription -------------------------------------------------------------------- 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. Correction The procedure now checks the correct field in the reply from NgDP. 200623/ALM-135: Mismatching error messages in validation report and history document ------------------------------------------------------------------------------------ The Mass dispatch history document has been changed to show a user-friendly error message when a recipient is not subscribed to Digital Post. The error message shown is “One or more recipients are not subscribed”/"En eller flere modtagere er ikke tilmeldt". 200854/ALM-145: Clarification of approval deadline -------------------------------------------------- The notes below clarifies the use of the approval deadline. What is the approval deadline for the mass dispatch? The approval deadline is 25 hours, and currently this cannot be changed. Can the approval deadline for mass dispatch be configured? No, currently changing the deadline is not supported. When a dispatch includes many messages, is there a risk that the approval deadline will be exceeded? The Mass dispatch process only starts sending letters when the mass dispatch has been approved. If the approval deadline is exceeded, it does not influence the mass dispatch. The dispatch of the messages is still started if it is approved after the deadline has been passed. The Mass Dispatch User Guide has been updated with a clarification of the approval deadline. 200939/ALM-151: The history document in CSV format cannot include the Danish characters --------------------------------------------------------------------------------------- The history document in CSV format cannot include the Danish letters æ, ø, and å from the letter title Correction This has been fixed as part of 201045. Danish letters were shown wrongly in Microsoft Excel because Excel assumes that CSV files are encoded in Windows-1252 by default. 200940/ALM-152: ShipmentState does not inform when a citizen is exempted from Digital Post ------------------------------------------------------------------------------------------ The ShipmentState field in the CSV history document does not inform when a citizen is exempted from Digital Post. Correction No correction has been made. "Not specified" in the CSV history document means that the message has not been sent because the recipient is not subscribing to Digital Post. This is clear from looking at the column “EboksSubscriber” where the value “false” shows that the recipient is not subscribing to Digital Post. When the recipient is not subscribing, the dispatch is not started, and hence dispatch state is not specified. The Mass Dispatch User Guide is updated with this description. 200937ALM-153: Mass dispatch returns technical error messages to end user ------------------------------------------------------------------------- It has not been possible to reproduce the exact same situation as described in the bug. Correction The CSV history document now shows the actual error message. In this specific case, the error will be shown as “Unknown error: recipient.is.closed Recipient with CPR 3110829996 is dead”. 201045/ALM-154: The CSV history document contains too much English information ------------------------------------------------------------------------------ The CSV history document has been improved to: - Use labels from the WorkZone data model as headers instead of column names. Headers can be localized by loading datadictionary extensions. - Use encoding Windows-1252 instead of utf-8 by default. - Format dates in the language of the report. To make it customizable. CSV history documents can be customized by developers. It is possible to customize columns and encoding. By default, CSV history document definitions are saved and can be updated in WZP_SETTINGS. There is no user interface for editing WZP_SETTINGS. 203074/ALM-157: Replies to messages sent as part of mass dispatch are stored on the dispatch case ------------------------------------------------------------------------------------------------- The issue occurs in Mass Dispatch when the messages sent allow the recipient to send a reply. Correction The problem is fixed by ensuring that the reply case (file_key and file_no) in the dkal attachment is set to the same case as the message was sent from (the journalize-case) instead of the dispatch case. This means that the reply will be stored on the same case as the message was sent from. It can now be controlled in the cases sheet of the recipient list workbook used during the mass dispatch. HFK2D ----- The following bugs have been fixed in this release: 200535/ALM126 Std. Mass dispatch returns english error messages to end user 200602/ALM144 NgDP - Unable to Repeat the Approve Mass dispatch user task 200622/ALM147 Std. Mass dispatch - Timestamps in PROHIST (CSV) are 2 hours bfore real time ============================================================================== New features introduced in this hotfix ============================================================================== No new features in this release HFK2D ----- IMPORTANT This hotfix has been released for specific customer installations and is not for general use. This hotfix installs necessary Mass Dispatch components for integration to Next generation Digital Post (NgDP) released by the Agency for Digitisation (Digitaliseringsstyrelsen) in conjunction with the NgDP-based hotfixes for WorkZone Process and WorkZone Configurator. The 2020.3 HFK2D consists of the following hotfixes: - 2020.3 WZMD HFK2D - 2002.3 WZP HFK2D - 2002.3 WZCnf HF02 All NgDP-related hotfixes must be installed and configured to be able to utilize the NgDP features introduced in these hotfixes. The WorkZone NgDP integration can be used in production when the Agency for Digitisation releases NgDP November 30, 2021. =============================================================================== Known issues and workarounds =============================================================================== Mass dispatch fails if the letter template has the state ARK (Archived) ----------------------------------------------------------------------- If the letter template document has the state ARK (Archived), the mass dispatch will fail. To work around this issue, you can set the state to UL (Locked). HFK2D ----- IMPORTANT --------------------------------------------------------------------------------- Due to unforeseen discrepancies in the test systems of the Danish Digitization Agency, the following issues with the new NgDP feature have been identified at the time of release of this hotfix: - Occasional HTTP500 response from NgDP - Failure to receive messages from borger.dk - Missing Business Receipt Reconstruction Events We will continue to handle these issues and all affected customers will be informed of our progress when the test systems of the Danish Digitization Agency enable us to continue our testing. Issues that are critical for the deployment and utilization of the NgDP feature will be patched in a future hotfix.