Fixed bugs in KMD WorkZone 2021.3
| Bug number | CS1385572 |
| Description | On a case with documents with several supplementary documents, an incorrect supplementary document could sometimes inadvertently be opened when the user double clicked in the list of supplementary documents on the documents detail tab. The error was caused by standard browser list behavior where the browser attempted to center the list of supplementary documents after the first mouse click. This resulted in the user clicking the wrong document with the second mouse click. |
| Correction | The standard browser behavior is now ignored and the user can open the intended document with the double click. |
| Bug number | 196907 |
| Description | When a user selected a smartmail in Microsoft Outlook, the smartmail sometimes showed wrong/incorrect labels (for example, depending on network bandwidth). |
| Correction | This has been fixed, and now a ‘please wait spinner’ is shown until the user interface is ready (applies to all WorkZone platforms). |
| Bug number | - |
| Description | AuthenticationException errors were shown when opening a Word/Excel/PowerPoint document. |
| Correction | Fixed. |
| Bug number | INC580730 |
| Description | When opening an empty document in Microsoft Word, a ScanJour error was incorrectly registered in the Windows event log. The error was only displayed in the event log and did not prevent users from working with their documents and saving them. |
| Correction | Opening an empty document in Microsoft Word no longer triggers an error in the Windows event log. |
| Bug number | INC3856866 |
| Description | Installer was checking 32 vs 64 bit during the uninstalling. |
| Correction | installer no longer checks 32 vs 64 bit during the uninstallation. |
| Bug number | INC3763098 |
| Description | MS Word was crashing when trying to convert a Word document to PDF using the Adobe Acrobat add-in. |
| Correction | Fixed. |
| Bug number | INC3990937 |
| Description | The time-stamp in the SmartPost history document using the Danish template was incorrect and did not correctly reflect the time the SmartPost process was started, sent or ended. |
| Correction | The SmartPost history document now reflects the correct time stamps when the SmartPost process was started, sent or ended. |
| Bug number | INC667837 |
| Description | Some reports generated through WorkZone Client contained an "Internal KMD A/S" text in the document footer. |
| Correction | The text has been removed from the template and reports will no longer contain this text. |
| Bug number | INC3863018 |
| Description | Calculations on dates that included milliseconds could not be handled properly when setting delays and deadlines for Case Activities.
Executing these calculations (for example < WorkZone date > minus Now) would result in an error with the message:
"Timespan |
| Correction | Data calculations can now be performed correctly in a DCR graph and without displaying the error message. |
| Bug number | INC4032025 |
| Description | Service workflows may get stuck in the state 'Initialize', which causes problems with some processes such as SmartPost processes and importing Interact forms. |
| Correction | General performance improvement: The workflow service (Workflow.svc) and the process service (Process.Svc) have been improved to be able handle multiple requests at the same time. |
| Bug number | INC3738702 |
| Description | Executing a case activity while SmartPost was running sometimes caused the case activities form to stop responding and graph to stay in the Running status. The form would only respond after the next Process service restart. The graph when executed from new form would return an error. The error was the result of the case being stuck in the Running status, which could be caused by the following situations: - A failure that prevented the activity state from reverting to the Persisted status, because of incorrect error handling. - Activity loops in DCR graphs that resulted in active running of the workflow which used up server resources until the Process service abruptly stop working. Similar behavior could be observed when a case was locked during processes execution (for example, SmartPost), where a user temporarily could not modify the case with an error message of not having the appropriate access rights. Automatically triggered Case Activities would be executed, but manually triggered activities could not. However, this behavior is by design and in place to temporarily protect the case from updates during the execution of actions such as generation of pdf reports. After these actions are completed, the user will be able to execute case activities again. |
| Correction | The management of error handling has been improved and activity loops in DCR graphs have been restricted to a maximum number of looped activities (50), which helps prevent Case Activity graphs from being stuck in the Running status. A new mechanism for handling DCR graphs has been introduced. If a graph is in the Running status for more than 5 minutes without signs of active activities, it will be considered idle, which enables users and the WorkZone system to perform operations on the graph. A DCR graph will be considered idle, even in the case of serious long-present network errors which could result in Case Activity graph not being able to switch back to Persisted status. Finally, the consistency among different execution paths of case activities was increased by setting a graph to status Running every time any activities inside of the graph are executed. |
| Bug number | INC4031901 |
| Description | In the English version of the documentation. The term "depreciated" was used instead of "deprecated" to describe a feature that is no longer in use. |
| Correction | Fixed. |