Viking 2.2.25 Release

17/09/2019

Enhancements 

• • Previously, all hierarchy fields added to a form were mandatory. An amendment has been done to allow hierarchy fields to be set to non-mandatory if required.

  • Dashboard – The Safe Act Observations (SAO) Report widget now shows data for a 6-month period if the date filter selected is 6 months or longer.  If the date filter is less than 6 months then data is shown for that time period only.

  • Scheduler – When processing a csv file for a job of type “records”, support for the update of existing records as well as creating new ones.

  • A new Name Update feature has been added which allows a global replace of names selected in ‘Person’ type fields. The user can select as many modules as required and the associated forms, Person fields and workflow steps for the name replacement can then be selected based on the module selection.

  •   Below enhancements are for REST/API:

    • • Added a new endpoint “records/totals” to include every form total counts for reducing the number of calls sent to REST API from mobile end, to optimise the performance.

      • Moved endpoint “commands/simple/{id}” name to “/result/{id}”? to make it completely separate from the original.

      • Changed current POST response to return appropriate body and keep Location information in the Header.

      • Reviewed API documentation and Swagger to ensure up to date

Support issues/fixes:

• • Amendment to ensure that fields from REVERSE_RECORD_LINKS added to the record list view can filter correctly:

    a.     Ensure that a reverse record hierarchy column can be filtered and sorted

    b.    Ensure that a reverse record keyword column can be filtered and sorted

    c.     Ensure that a reverse record field column can be filtered and sorted

  • Amendment to allow records to be deleted from the “My Activities” view

  • When a record is cloned, ensured that any linked records to the original record are also linked to the cloned record.

  • Prevented an error in the Inspections module caused by users being able to remove Questionnaire fields thus causing an error with the Grand_Score field which cannot be null. Now users are prevented from removing a questionnaire field (if it is the only one) if there is a Grand_Score field present.

  • Adjusted the row number by one in the notifications of the records import feature to match the clients’ concept of the row in Excel. The clients’ expectations is that it starts at 1 but the program code was using zero.

  • Amended issues with PERSONFIELD lookup from a record matched by a hierarchy value.

  • Further amendments for Viking integration with v4.

  • Security fix: sanitise input for RICHTEXTAREA field.

  • Investigate and change max DB connection to sensible number.