Viking 2.2.29 Release

15/10/2019

Enhancements 

• • Updated the pop-up message when closing the form editor without making changes displayed in Japanese (if logged in as a user with Japanese locale).
  • Ensured that ‘Date’ type fields are set to the correct default when creating a new record (if a default date has been specified in the Form Editor for the field). For existing records, a new “Date” field added will default to the record creation date.
  • Improved record list fetch performance.
  • Column widths have been expanded to fit the content to a specified maximum width of approximately 400 pixels. When hovering over a table cell, tooltips are displayed for the following types: Text types (TEXTFIELD, LABEL, TEXTAREA, RICHTEXTAREA etc); Combo boxes, option groups, and multi-select fields; Person fields and multi-select person fields; Risk ratings; History; Questionnaires; Other, e.g. fields that do not have special rendering, this includes grand score.
  • In the scheduler UI, added a new checkbox field for “Set last modified date?” and if true, then display a combobox of date fields which can be used to choose what date should be used for last modified. This is so that after a migration has been completed, the mobile app will not find every record as recently modified.
  • In the Scheduler UI, in the field mapping dialog, if the field type selected is a RISKRATING field then ask the user to select the format. Currently we only need to support one format with is “Rating”. This means the customer will upload with an integer of the actual Rating, eg: 21. (Note, this is not the id of the rating but the value).

Support issues/fixes:

• • Record list filter fields for hierarchies showed values the user did not have access to (when hierarchy restrictions had been applied to users).
  • Ensured a deleted record is removed from the record list.
  • Ensured that any hierarchy changes and changes to roles are immediately reflected in records (ie that the sync to the database occurs on update).
  • In the Form Editor, Automatic Progress Rules were not displaying for rules based on Record links. Also the wording for rules based on integer fields was incorrect. Now displays in the format:

a) “Progressed from {src_workflow_step} to {dst_workflow_step} when {no/any/all} in {recordlink_field} are {linked_record_workflow_step}” for Record Link rules.

b) “Progressed from {src_workflow_step} to {dst_workflow_step} when the number in {int field} first occurrence {the number set}” for Integer rules.

• • Amended issue which was causing duplicated COMBOBOX values.
  • Amended an issue which prevented ‘users’ from syncing to the database if the email was null and the user ID was not specified.
  • Amended an issue caused when the lookup type was “From a Record matched by a hierarchy value and the lookup form is set to itself eg. Risk Assessments àSWMS.
  • When the “forgot your password” link is clicked ensured that the email text sent to the user is in Japanese for a user with Japanese locale.
  • Amended error experienced when adding a ‘Date’ field condition to Automated Advancing of Workflow Rule.
  • The dashboard database and REST has been updated to the latest version. Regression testing done to ensure all is working correctly.
  • Enableb type ahead filter for Combobox with “add new” enabled.
  • Amended issue with Admin tabs when two users access the admin view at the same time.
  • When the name format is changed, ensured that this change is reflected in the Training Matrix on the dashboard.