Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This quarter we've got a number of exciting new features and enhancements to improve your user experience within the system, which will be available in your Test environment on 3rd September 2022 and will be available in your Live instance on 17th September 2022

List of release items:

Table of Contents
minLevel1
maxLevel7
stylenone

1. Performance upgrade to Incident pages

A host of performance and stability improvements will be made when creating and saving an Incident and in the Incident Details page for a better user experience.

Additionally, you will be able to log new incidents from the left-hand menu and apply updates to existing Incidents in the Register with minimal delays.

2. Performance indicator logic to be improved for Incident/Compliance Actions

The existing logic for the performance indicator has been improved to reflect the target calculations similar to the Camms.Risk application. The improved logic calculation takes the current and targeted dates into consideration, in deriving the performance state of an action, providing more accurate and reliable insights into the action progress status.

...

To configure the performance thresholds:

  • Navigate to Menu > Administration > Configuration > Action Progress.

  • Set values for the ‘On Track’ and ‘Off Track’ fields. By default, the following values will be set:

    • On Track >= 90

    • Off Track <= 70

    • Monitor: < 90 and >= 70.

...

  • On Track (green) – Indicates that the % of completion of the Incident Action is on track.

  • Monitor (amber) – Indicates that the % of completion of the Incident Action requires close monitoring to get the Incident Action back on track.

  • Off Track (red) – Indicates that the % of completion of the Incident Action is off track.

  • N/A (grey) – Indicates that the performance of the Incident Action cannot be calculated.

...

Performance Calculations

  • Where an Action's status is ‘Completed’, the performance would be always set to ‘On Track’.

  • Where an Action's status is either ‘Deferred’ or ‘Ongoing’, the performance would be always set to ‘N/A’

  • Where an Action has the status ‘Not Started’ or ‘In Progress’, the performance will be calculated as below:

    • Performance = (Percentage Complete / Target Completion %) * 100

    • Percentage Complete = The actual performance of an Action based on the Percent Complete value added (between 1 – 99). This is added by the user under the ‘% Completion’ field within the Incident Action.

    • Target Completion % = Target will be calculated considering the Start and End dates with linear progression, whereby, Performance would be 0% on the Start Date and 100% on the End Date. 

    • Target = [(Current System Date - Action Start Date) / (Action End Date - Action Start Date)] * 100%

...

Info

Note: The Actions by Progress Status, Incident Actions by Progress Status, Actions by Type, and Overdue Actions widgets in the dashboard and their drill-down screens, will reflect the updated  performance indicator, based on the above logic.

3. Default field name for Documents uploaded via the Documents object

A default field name will be displayed for documents uploaded via the Documents object. 

...