Release Overview

• When: Friday Apr 9, 6pm
• What:
  • • Sensitive Events
    • Public Liability
• Post-release verification: Friday night, Saturday, Sunday
• The system might not be 100% stable during the verification period if issues are found.

Sensitive Events

Key Changes Summary:

• New settings to:
  • Provide additional control over when notifications are sent.
  • Specify the minimum number of Sensitive Users to be assigned to Sensitive Events.

• Ability to control whether Sensitive Events can be reported via the Web Portal.

• Enhancements to notification messages to make them clearer and more consistent.
• Ability to assign multiple Sensitive Users to an event
  
• Investigators and Reviewers for Sensitive Events must also be a Sensitive User assigned to the event.
• Confirmation messages when changing an event from Normal to Sensitive to vice versa.
  
• Report enhancement to show if someone assigned to a Sensitive Event is no longer a Sensitive User.
• New governance report for Sensitive Events.
• New user group profile permission for marking events as Sensitive Events.
  
• Corrective actions can be assigned to people who are not Sensitive Users assigned to the event (but they cannot see details of the Sensitive Event).

Public Liability

Scope: View Jira issues list (Internal Use - Jira access required)

Who gets this update?: all clients who have the Locations feature enabled (this feature was introduced with the Locations and Asbestos release last August)

Key Changes Summary:

• New Public Liability and Property Damage event categories.
  
• New Involved Person Type filter for events.
  
• Additional filters for event reports.
• Categorisation details added to Event Registers - All Events report.