Rizikon Assurance 2.2 release note
Rizikon Assurance has been updated to version 2.2 as of 17th February 2020. This release includes:
More source information has been added to scorecards, and users can now navigate directly from a scorecard to the origin of the underlying data, and source information tool-tips have been updated to show the user that provided the data.
This workflow improvement allows managers to track the provenance of the data on scorecards, and drill down to locate and remedy the highest priority issues.
All attachments added to questions will be scanned for malicious code. There have been some user interface changes to display the different statuses of attachments, which can be seen by:
Blue icon (unscanned)
Grey icon (scanning)
Green icon (scanned with no malicious code detected)
Red icon (scanned with signs of malicious code)
Attachments will be unavailable for download while being scanned or in the event of an attachment being suspected as containing malicious code. Once the upload has completed, users do not have to wait for the scan to complete before leaving the page as normal.
Bulk Upload Improvements
Unnecessary mandatory fields have been removed from the bulk importing templates to improve the user experience of this feature, specifically the "Assessment Status" column. The new templates are available from the bulk data upload page as usual.
Furthermore, a new "Default Scorecard" field has been added to the Organisations upload template, allowing this information to be set quickly and easily from a CSV file.
Multiple bugs have been fixed, including the display issues with the 6x6 Criticality dashboard displaying old values, especially when the default scorecard has changed. Furthermore, users will no longer see a "Processing refused" error when they have been appropriately logged out due to inactivity, and the "impact" column in the bulk data upload template for Organisations should now also work as intended, allowing users to set Organisation Impact in bulk.
We have also made some changes to the way we handle emails, with the intention of improving reliability and delivery.
If you have any questions or issues, please let us know.
If you have any issues, please contact us at firstname.lastname@example.org