=============================================================================== Release Information =============================================================================== KMD WorkZone Client version 2020.1 Released November, 2020 Version information: KMD WorkZone Client 20.1.20323.1 =============================================================================== Prerequisites =============================================================================== Supported browsers: - Internet Explorer 11 - 32 bit x86 and in non-compatibility mode - Google Chrome version 71 or later (32 bit and 64 bit) - Microsoft Edge 18 or later (32 bit and 64 bit) Minimum supported screen resolution: 1440x900. Client OS: - Windows 10 (32 bit x86 and 64 bit x64) Microsoft Office: - Office 2016 (32 bit x86 and 64 bit x64) - Office 2016, 365 subscription (32 bit x86 and 64 bit x64) - Office 2019 (32 bit x86 and 64 bit x64) WorkZone for Office: - WorkZone for Office 2020.1 Server: - Microsoft Windows Server 2016, IIS 10.0 - Microsoft Windows Server 2019, IIS 10.0 - For the Process module: * WorkZone Process Server 2020.1 must be installed and configured on the server WorkZone Content Server: - WorkZone Content Server 2020.1 KMD WorkZone Process: - KMD WorkZone Process 2020.1 =============================================================================== Installation =============================================================================== See documentation on http://workzonesupport.kmd.dk/ =============================================================================== Upgrade Information =============================================================================== Important: Upgrading to KMD WorkZone Client 2020.1 is not possible from versions before 2018.0. You must uninstall the previous version and install KMD WorkZone Client 2018.2. Important: WorkZone Client configurations created in WorkZone Client 2017 or earlier versions are no longer possible to migrate, and they will be lost when you upgrade WorkZone Client to version 2018.1. This is a consequence of the fundamental dashboard improvement and new functionalities introduced in release 2018. WorkZone Client configurations created in WorkZone Client 2018.0 will be maintained after the upgrade except the settings applied to dashboard and navigation pane. This is a consequence of the multiple dashboard functionality introduced in release 2018.1 Configurations created with WorkZone Client 2018.1 and newer will be retained fully. Important: When you access the KMD WorkZone Client from a client after upgrade from an earlier version than KMD WorkZone Client 2016, you need to clear the browser cache. For more information, see the Administrator's Guide for WorkZone Client. ============================================================================= Documentation ============================================================================= Release documentation is available on http://workzonesupport.kmd.dk/support/dokumentation-workzone-client/ The documentation includes: - Readme (this document). - Administrator's Guide for WorkZone Client (including installation guidelines and Support Matrix). - User's Guide for WorkZone Client (including description of the new features in this release). ============================================================================= Bugs fixed in this release ============================================================================= For an overview of the reported bugs fixed in this version, see http://help.workzone.kmd.dk/ReleaseNotes/2020_1/FixedBugsList/FixedBugs.html =============================================================================== Bugs fixed in version 2020.1 Hotfix 1 =============================================================================== Data in Custom fields of type Contact could not deleted A data in a Custom Field of type Contact placed on a Case, Contact or Document detail page could not be deleted and resulted in an error message with the text: Could not find a property named ‘NameCode’ on type ‘Som.RecordA’. Now data entered in Contact Custom Fields can be deleted. Case activity list in the Preview pane was not correctly updated When a case activity was selected in the Activities tab on the Case detail page and the Preview pane was opened, the activities were displayed for the selected case activity, however if another case activity was selected afterwards, the preview pane would still display the activities of the first case activity while displaying the title of the second case activity. Now, the preview pane displays the activity data of the case activity currently selected in the Activities detail tab. Unable to navigate to case from document detail tab Case references After adding a new case reference toa document on the Case references detail tab on the Documents detail page, it was not possible to open the case from the Documents detail page. Now, navigation to the selected case is no longer prevented from the Case references detail tab on the Documents detail page. =============================================================================== Bugs fixed in version 2020.1 Hotfix 2 =============================================================================== Unavailable values in drop-down lists in searches In searches, it was not possible select values in drop-down lists where the list values in the database had been marked with the SELECTABLE=FALSE property. It is now possible to select these values in searches only, for example searching for the OMJ document type or the OMJ case type. --------------------------------------------------------------------------------------- Incorrect display of forward slash in Case group field When creating a new case and selecting the case group, if the case group text in the drop-down in the 'Case group' field contained a forward slash (/), the case forward slash would be represented with the HTML-code / instead of a forward slash. Now, forward slashes from the drop-down in the 'Case group' field are correctly displayed as forward slashes. ---------------------------------------------------------------------------------------- Reimporting a Json configuration file from a previous version created duplicate configurations When a configuration json file was imported again into Workzone and the export json file had been created from a previous version of WorkZone, an identical configuration was erroneously created, resulting in two identical configurations existing in WorkZone 2020.1. Now, when an export Json configuration file from a previous WorkZone version is imported again, duplicate configurations will not be created. =============================================================================== Bugs fixed in version 2020.1 Hotfix 3 =============================================================================== Default access code not assigned to case group on case creation Service Now number: CS1119214: BUG 5804 - SUM nr 323 Kritisk fejl. Opret sag - vælg sagsgruppe - læseadgang obligatorisk When selecting a case group in the Select case group form during case creation (by clicking the Select case group icon to the right of the Case group field), the access code on the case was not assigned as the default access group for the selected case group. If the case group was selected from the dropdown list in the Case group field (by clicking the Select case group field) , the access code on the case was assigned correctly as the default access group for the case group. Now, during the case creation process, the access code on the case will be assigned as the default access group of the selected case group, regardless of how the case group was selected.