Fixed bugs in KMD WorkZone 2022.0
Bug number | 199211 |
Description | Widgets originally placed in the "Widgets crossing this area will not be rendered" area in the Dashboard configuration form and saved on the dashboard, caused the dashboard to fail when they were subsequently moved into the render area in the Dashboard configuration form. |
Correction | Widgets can be placed in the "Widgets crossing this area will not be rendered" area in the Dashboard configuration form and after saving the dashboard, can be moved in the render area without causing the dahsboard to fail. |
Bug number | INC4098343 |
Description | The time in a DateTime custom field was one hour backward when the activity was executed with the "Update using now+PT1H" command. |
Correction | The Datetime custom field now calculates the date and time coorrectly when using the Update using now+PT1H command |
Bug number | 198821 |
Description | On a case with a case activity and a DCRGraph referencing a DateTime custom field on the graph, changes to the value in the DateTime custom field would not be registered correctly when the DCRgraph was re-run. The issue was caused by the DCRGraph performing incorrect time zone updates. |
Correction | DCRGraphs referencing DateTime custom fields now register changes to the DateTime custom field values correctly. |
Bug number | 197171 |
Description | After a case search had been performed, filtering the Primary Party column in the search results detail tab did not display any results despite the presence of search results that satisfied the filter conditions. The issue was caused by the filter function being erroneously applied to several incorrect elements and not to the search results themselves. |
Correction | The filtering the Primary Party column in the search results detail tab is now applied correctly to the search results. |
Bug number | INC4026306 |
Description | A PDF conversion policy could not be saved if any value other than |
Correction | The PDF conversion policy can be saved for all defined values in the Document last updated field. |
Bug number | 196018 |
Description | It was not possible to define a standard letter case to a Smart Post process or define a default case number to an e-boks service workflow. The search/filter feature in the StandardLetterfileNo field on the SmartPost - Process parameters form in Configurator > Process > Processes did not locate any cases a user could add as the standard letter case. Likewise, the search/filter funciton in the DefaultCaseNo field on the Service workflow paramters form in Configurator > Process > Service workflows also did not locate any cases a user could add as the defalut case number to a service workflow. |
Correction | The search/filter function in the StandardLetterFileNo and DefaultCaseNo fields now serach and filter the list of cases in each field, enabling the user to select from the filtered list. |