For release on: 16/6/2022
The following release notes refer to planned amendments that are subject to final testing prior to being released.
- Changes have been implemented to allow Contractors access to multiple schemas. The second and subsequent customer schema will be able to invite the contractor in the usual way and the contractor will be sent an email containing information regarding access to the additional schema with instructions on how to log in. Changes have also been implemented to allow contractors/users with multi-schema access to be correctly archived and restored.
- Apply sorting in alphabetic order for the schedule names in Administration – Scheduled Record Creation.
- Apply sorting in alphabetical order to the list of forms in each module in Administration – Form/Workflow Definition.
- Remove the ability to add multiple recipients when sending an invitation to an external user.
- An “Upload” button has been provided for TEXTUAL_QUESTIONNAIRE fields to facilitate directly uploading attachments and linking them to the question. This alleviates the need to upload files to the record and then attach them to the relevant questions.
- When a CHECKBOX field has been configured with the display option as ‘caption text’ and it is selected to appear in a RECORDLINK column table, ensure that it is rendered correctly with the name of the CHECKBOX field displaying if the check box is checked and blank if unchecked.
- Ensure that all values are available for selection in a record for muti-select type fields when the lookup type is configured as “From a Record marched by a hierarchy value” and the data source is an OPTION_BUILDER field.
- Ensure that records created in the mobile app which break the automatic versioning criteria are not saved.
- Dashboard – Correct issue of hierarchy and date range filters not being applied to a generated link when the Dashboard tab selected was not the first tab.
- The ‘Hierarchy Access Ignore Mode’ (in Administration – Access Control – General) has been corrected to ignore all hierarchy restrictions of all external users, all internal users or both internal and external users. For example, when access control is configured to ignore internal hierarchy restrictions and if an internal user is logged in then all hierarchy restrictions (both internal and external) need to be ignored. Similar logic is applied when an external user is logged in.