Fixed bugs in KMD WorkZone 2020.1


WorkZone Content Server: Incorrect references to supplementary documents when importing from another database

Bug number CS0889529
Description Incorrect references to supplementary documents when importing from another database when documents with references to supplementary documents were imported into WorkZone from another WorkZone database, the import would fail or incorrect references to supplementary documents were used, resulting in an erroneous document in the target WorkZone database.
Correction Now, importing documents with references to supplementary documents will import the correct documents.

WorkZone Client: Wrong summary displayed when editing saved search

Bug number CS0793897
Description When a user edited a saved search, an incorrect summary of the search was displayed.
Correction The correct summary is now displayed when editing a saved search.

WorkZone Process: SmartPost dispatches may fail if the case has a complex write access (update) code

Bug number 176459
Description If you try to send SmartPost messages or receive SmartPost messages on a case with a complex update code, the dispatch may fail.
Correction Fixed

WorkZone Process: WorkZone Client hangs if the WorkZone Process configuration fails

Bug number 176461
Description If errors occur during configuration of WorkZone Process, WorkZone Process is uninstalled and the WzpSvc application pool is removed. This causes WorkZone Client to hang.
Correction The application pool is no longer removed.

WorkZone Process: SmartPost dispatches may fail if the case has a complex update code

Bug number 176482
Description If you try to send SmartPost messages or receive SmartPost messages on a case with a complex update code, the dispatch may fail. This is corrected.
Correction Fixed

WorkZone Process: SmartPost fails if a content control is in a table cell

Bug number 176712
Description SmartPost failed if a content control is in a table cell.
Correction Use the letter date content control in at text box, then SmartPost works.

WorkZone Process: Upgrade fails if two dispatchers have the same name

Bug number 176736
Description WorkZone Process: Upgrade fails if two dispatchers have the same name.
Correction Fixed

WorkZone Process: 'Case number' column is missing in Processes Overview

Bug number 176749
Description The 'Case number' column is missing in the new version of the Processes Overview.
Correction The 'Case number' column has been added.

WorkZone Process: SmartPost fails when e-Boks returns error code 1000

Bug number CS0852288
Description In case of operational issues at e-Boks, e-Boks returns an error code 1000 (internal server error) to WorkZone. The SmartPost process fails but the error was not reported if the SmartPost action was set to Retry. For example, the server error may occur after the message is received but before the status/receipt is reported back to WorkZone.
Correction The SmartPost action has been changed so that an e-Boks error code 1000 sends errors immediately (Notify) instead of trying again (Retry), which was the default setting. Notify ensures that the process owner will be notified about the failed dispatch. The process will be completed, and the history document will be generated so that you can see the status of each dispatch.

WorkZone Process: Upgrade results in wrong number of dispatchers

Bug number 177607
Description After upgrade, the number of dispatchers is incorrect.
Correction Fixed

WorkZone Process: Misleading description in the Print SmartPost message locally smarttask

Bug number CS0829786
Description The description in the smarttask sent to users when a SmartPost message is sent to local print was misleading.
Correction The description in the smarttask has been revised.

WorkZone Process: The SmartPost history document only shows 2 of 4 documents

Bug number CS0817227
Description When sending a letter through SmartPost and attaching several documents, you can only see the first two documents in the history document.
Correction Fixed

WorkZone Process: SmartPost fails when the 'Send attachments as separate documents' check box is selected

Bug number 175521
Description SmartPost fails when the 'Send attachments as separate documents (only e-Boks)' check box is selected.
Correction Fixed

WorkZone Process: Upgrade 18.2 -> 20.1 - SmartPost cannot send to OneTooX

Bug number 175545
Description If you upgrade a system where the Doc2Mail dispatcher is present, the replacement dispatcher OneTooX will be missing the print types.
Correction Run the script OneTooXPrintType.sql located in KMD\WorkZone\Process\Config\Scripts in sqlplus after the configuration is complete to add the missing print types.

WorkZone Process: Process owner did not receive notifications

Bug number 175555
Description The process owner did not receive a notification even if the process owner was selected on the 'Notifications' tab in the 'Start submission (Extended)' dialog box.
Correction Fixed

WorkZone Process: The Process Configurator removes the Process site when configuration fails

Bug number 176095
Description When upgrading SmartPost, the Workzone Process Configurator removed the Process site in IIS which caused WorkZone Client to fail loading.
Correction Fixed

WorkZone Process: When "periodeskift" takes place, the loading of process packages fails

Bug number 176129
Description When "periodeskift" takes place, loading of process packages fails. Correction Fixed
Correction Fixed

WorkZone Process: Missing parenthesis in the SmartPost dialog box

Bug number 176209
Description Missing parenthesis ) in label in the SmartPost dialog box.
Correction Fixed

WorkZone Process: e-Boks dispatch fails with a null exception

Bug number 178918
Description When e-Boks fails with one of the error codes that is associated with the action 'Retry', it will not retry. Instead the dispatch fails with a null exception.
Correction Fixed

WorkZone Process: A user task is sent saying that the dispatch went wrong even though the history document says it went well

Bug number 178926
Description In rare cases, deletion of the original document fails without being flagged. This causes the history document to report that the dispatch was successful but a user task will be sent saying that something went wrong. It does not mention that it is the deletion of the original document that fails.
Correction This has been corrected and the user task indicates that the document deletion has failed.

WorkZone for Office: Emails created in Outlook are not sent

Bug number JM
Description If the Outbox folder is selected in Outlook, and you create a new email, the email is not sent. It stays in the Outbox folder.
Correction Fixed

WorkZone for Office: Custom default values are not saved

Bug number FSMI
Description If you create a new document that contains a field with a custom default value, and you then save the document in WorkZone, the value is not saved. This issue is relevant to Microsoft Word, Excel, and PowerPoint.
Correction Fixed