05/06/2019
- Enhancement that allows record links within textual questionnaires to be shown in the pdf document when the record is exported.
- Ensured that when a form is cloned all notifications and email templates are also cloned and work as expected. When a cloned form is deleted, ensured that all notifications and email templates are also deleted.
- Customisation – Allowed for other ways of populating the hierarchy of a record other than defaulting to the author/creator of the record. Options allowed for:
• Auto-populate from the user creating the record” (default)
• Auto-populate from a field on the form
• Leave blank
- Amendment made to the Equipment Maintenance module to ensure that all “service” records are being linked to the correct Equipment Maintenance record.
- When changes are made to “users” records, prevent duplicated audit log entries.
- Fixed an issue with answers to textual questionnaire fields completed in the mobile app not being synced to the browser.
- Fixed an issue which prevented the successful export of hierarchies with dependencies.
- Fixed an issue with answers to textual questionnaire fields completed in the mobile app not being synced to the browser.
- Fixed an issue which prevented the “Recurrence” and “Share” buttons not being visible in a record in full screen mode.
- Prevented an error from being produced in the record list view when clicking on the “Manage” option in an empty module (with no forms). Now the message says “No form is selected”
- Amendment to exclude a RECORDLINK field in a template from being exported when the template is being imported into a different schema (as RECORDLINKs are usually specific to a form within the schema they are created in).
- Fixed an issue to prevent deadlocks when creating or editing a user account.
- Ensured changes done to forms and modules are being handled by MQ and synced to MongoDB
- Amendment done to ensure that when a record is deleted which is linked to another record, it is removed completely.
- Fixed an issue to prevent a section template with LINK fields from producing errors when the section template was added to a form.
- Ensured that the Training Time values display correctly in the “Training Management” tab in Administration.
- Removed invalid characters from Hierarchy types when exported as a template and ensure the template can be re-imported without the invalid characters.
- Fixed an issue to prevent values being cleared from fields that had visibility conditions applied. This was causing a “save record” prompt when accessed by a user who could not see the field as it was being cleared.
- ‘Old’ and ‘New’ values of ‘MULTI’ type fields (eg MULTIPERSONSELECT, MULTICHECKBOX etc) are now being shown in the audit log when these field types are amended in a record.
- Widened the length of TWINCOLUMN fields so that longer titles are visible (eg Occupations).
- For Viking schemas integrated with v3/v4, ensured that Viking is sending the Employee Id of a user and that this is being received in v3/v4.