Viking 2.2.19 Release

07/08/2019

Enhancements 

• • API – previously when posting a record that has unrecognised field options, the record was imported and the fields with unrecognised options were left blank/null (eg COMBOBOX, OPTIONGROUP etc type fields). This has been amended to allow handling of unrecognised options in four different ways, according to the POST parameters included with the request:

a) Do not import the record and return a validation failure message

b)Import the record and leave the field blank

c) Create the unrecognised values as option/s for the fields and mark these option/s as archived

d) Create the unrecognised options for the fields and leave it to the end user to manually archive them if required.

• • Support the display of images in the table of linked records.

  • Added a field for “Doc No” to the export templates of records.

  • Extended functionality of CLONERECORD wizard, to allow selecting groups to assign cloned actions. Selecting one or more groups will assign the cloned action all members of the selected group. This also ensures that if a person is in multiple groups, they will not get a duplication of assignments of the same record.

  • Mapping of multiple fields for Actions types and subject to be set automatically –

a) Allow for setting multiple fields in the same record. Previously only one field could be set.

b) Map text fields from the parent record to the sub record. Eg: set the Description of an action automatically from the Brief description of the parent incident.

• • Amendments for additional configurations for PDF export of records. The following options are presented:

a) Title

b) Sections to be included

c) Append linked records as separate pages

d) Signature Page

e) Some Improvements to Home Page to ensure consistency of displayed items

f) Support importing Hierarchy Access via the integration job

Support issues/fixes:

• • There was previously no Yes/No confirmation prompt for cancelling out of the Form Editor. Added a prompt pop-up if there are unsaved changes. The form will be saved if ‘Yes’ is clicked and discarded if ‘No’ is clicked.

  • Amendment to ensure that the value from a READER field which has been set as mandatory can be cleared.

  • API – When an attachment from a record is deleted and the deleted file is again posted via the API, an error was generated when a user attempted to attach it to a record. This has been amended.

  • Sped up the process when a failed post of a record is marked as an error by the Message Queue.

  • Changes to ensure that SSO users with or without a password can be handled correctly in the database.

  • Changes to ensure the Message Queue can handle the situation where a parent record is posted first (via the API) without the linked (child) record existing. The Message Queue will attempt to link the child record 5 times until it is found and will then link it to the parent record.