myosh Viking Feature Updates July 2019

Viking

New

• Users can now exclude archived records from record lists. This means record lists will now load significantly faster for customers with 10s of thousands of closed documents.
• Amendment done to ensure that selections and un-selections done in a Multi Select Check Box field are recorded in the audit log (eg Incident Classifications).
• Ensure that images added to inspections work correctly in the API.
• Support for EMAIL_THIS field type in mobile. Ensure that an email created in the API can be received.
• Enhancement that allows record links within textual questionnaires to be shown in the pdf document when the record is exported.
• Allow 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
• ‘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.
• Checkbox added to “Ignore Hierarchy Restrictions” for the Person type fields (PERSONFIELD/MULTISELECTPERSONFIELD/TWINCOLPERSONFIELD) in the form configuration for the situation where a user has hierarchy restrictions applied and is also limited in the field (“Show in Person Field”) to seeing only a subset of users. This could cause an issue in some circumstances – eg. selecting an HR person for a confidential incident. The addition of this checkbox now allows hierarchy restrictions to be ignored in some circumstances.
• Automatic Versioning – ensure new versions start at the first workflow step
• An “Expiry Date” field has been added to the “News Feed” in the Home Page. News items will display until this date after which the status will change from “Published” to “Expired”. A column for “Publish Status” has also been added to the “News Feed” view. The “Publish Status” can be either “Not yet published”, “Published” or “Expired”.
• An “Author” field has been added to the “News Feed” in the Home Page. The “Author” is displayed next to each corresponding item on the Home Page.
• Allow a user to click on the hyperlink from a LINK field in the record view and be taken directly to the record.
• Hide the field detail of the audit log in a record if access is restricted. This was an issue when users were restricted from viewing certain sections of a form but could view all audit log changes.
• Removed the limitation which prevented field/s from appearing in the Record List if the section they were in was not added to every workflow step in Access Control – Section Access.
• Disallowed a workflow step to be archived if there are existing documents in that workflow step. There is a warning message displayed asking the user to either progress or revert the records.
• Ensure that notifications which have “Send Once” selected in the notification properties are sent once only for a particular record and not on a continuing basis.
• Notification mechanism changed so that it removes the need to nominate a triggering workflow step if the triggering event for the notification is a “date field”.
• The UI for the configuration of automated workflow rules has been changed. The different rules are now aligned, making it more user friendly to read and configure. The format for the following type of rules were also changed:
  • • • • • • Date field condition
            • Record Link field condition and
            • Integer field condition
• A “Restore” button was added to the “Edit Hierarchy Type” screen. This button will allow users to un-archive hierarchy values when necessary.
• Development was done to support the cloning of “PDF Export” and “Word Export” field types
• The workflows steps that form part of the workflow definition can now be added as keywords to the record list in configuration. This makes it possible to see the date the workflow status of a record changed as this date will now be visible as a column in the record list.
• TEXTUAL_QUESTIONAIRRE fields that are not visible due to visibility conditions will not count towards the Max possible score or percentage of the GRAND_SCORE field.
• For a RECORDLINK field, when the “select” button is clicked to view records available to be linked, the selected records table now has the same fields and display as the table of records available for selection (screen shot below to illustrate).

Mobile