Viking 2.2.28 Release

08/10/2019

Enhancements 

• • Added a ‘Clear’ button to allow the signature field to be cleared.  This functionality was available in the app and has now been added to the web version.

  • The validation added for the ‘Date’ field to force entry of current or future date has been amended to only apply the validation if the date field was previously blank.

  • For integration jobs run in the Scheduler, there is now support for the OPTIONGROUP field type when a column in the csv upload file is mapped to an OPTIONGROUP field in Viking.

  • For integration jobs run in the Scheduler, the source ID can now be provided in the import file. If a record with the matching source ID is found it is updated and if it does not exist, it is created by the integration process.

  • New customised widgets for frequency rates to show a 12 month performance to month end with a comparison to the previous year for the same period.

Support issues/fixes:

• • Amended an error which occurred when attempting to open the user record of an external user whose hierarchy restriction had been removed.

  • Fixed an issue with filters in the record list not working correctly.

  • Dashboard – amended issue with column widgets showing decimals in the totals when configured to show as whole numbers.

  • Support for export/import of Textual Questionnaire and Numeric Questionnaire field types in the record export/import feature.

  • Amended error appearing when full screen mode used to display records.

  • Issue with Invitation section not being visible in full screen mode has been amended.

  • Amended issue with form changes not ‘sticking’ after saving if the user changes to another module in the module selection and then comes back to the original form.

  • Fixed issue with records not automatically processing to the next workflow step due to there being a rule in the automated workflow which applied a “NO” condition on the linked record (eg, ” [no] in [linked form] are [open]” ).

  • When a PERSONFIELD was configured in the form editor to use the option “Users with the same value in the hierarchy type: [External Hierarchy type]”, it produced an error when a person logged in as a schema user accessed the record. This has been corrected.

  • Separated the recordlink_recordlist_field for fields and hierarchy types.