...
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 11th September 2021 and will be available in your Live instance on 25th September 2021.
List of release items:
|
1. Ability to trigger notifications based on custom date fields |
This feature provides the ability to trigger notifications based on custom date fields and the ability to combine date fields with other fields to setup a more advanced logic as the trigger criteria (e.g. triggering a notification 5 days before a certain date, if the incident is still open).
Two new operators (BEFORE and AFTER) have been introduced, that can be used when incorporating custom date fields to custom trigger criteria.
How do you configure this?
Navigate to 'Menu > Framework > Incident Settings > Notifications' and click on 'New' to configure a new notification.
To incorporate custom date fields within the custom trigger criteria of your notification, you will need the ‘Custom Trigger Criteria Configurations’ editor. To do this, select any of the below notification types along with the ‘Trigger Criteria’ as 'Custom Trigger Criteria':
Incident
Investigation
Resolution
Close
Risk
Submission
Custom
Build your custom date related trigger criteria in the ‘Custom Trigger Criteria Configuration’ editor using the following format. You can use the 'Variables' and 'Operators' dropdowns in the ‘Custom Trigger Criteria Configuration’ editor.
({[Operator]([Date field],[Timeframe],[Timeframe unit])})
...
| Info |
|---|
Note: You can combine your custom date-based trigger criteria with other criteria by using operators like AND, OR, etc. Refer the User Guide for more details. |
How will this work?
Once the notification is configured based on the date-time field and saved, the notification will be triggered and sent to the configured recipients on the resulting date(s) based on the trigger criteria.
If you save a notification criteria with an invalid syntax, a warning prompt appears “The trigger condition entered in Custom Trigger Criteria is incorrect. Please check the User Guide for further guidance”.
...
You can alternatively click on the 'User Guide' hyperlink in the tooltip to get navigated to the same page.
...
2. Support for custom trigger notifications during incident submission and resubmissions |
This feature will let you trigger notifications based on user defined custom trigger criteria for Submissions and Resubmissions.
How do you configure this?
Navigate to 'Menu > Framework > Incident Settings > Notifications' and click on 'New ' to configure a new notification.
‘Submitted’ and ‘Resubmitted’ will appear as an option in the ‘Trigger Criteria’ dropdown when you select any of the following as ‘Notification Type’:
Investigation
Close
Risk
Resolution
Custom
Review
...
Once ‘Submitted’ or ‘Resubmitted’ is selected as the ‘Trigger Criteria’, the below additional fields will appear in the notification configuration area only for the ‘Custom’ Notification Type.
‘Type’ dropdown – This will list all the Incident Types configured under Incident Settings > Type
'Object’ dropdown – Upon selection of the 'Type', all the objects in the relevant workflow will be displayed
...
| Info |
|---|
Notes: The functionality of previously created notifications will have no impact from this modification.
|
3. View additional details on API errors via the error notification |
This feature will enable you to view additional API error related information via the error notification, providing a better understanding on the encountered API error.
...
Request Body
Response Body
Method – only API
API End Point – only API
Headers
Parameters
Authorisation
Time To Deliver
Time Stamp
Response Source – only API
Retry Attempts
Error Log
API Notification
How do you configure this?
A Notification Template needs to be created for an API Notification Delivery Failure via 'Menu > Framework > Incident Settings > Notification Template'.
Select the ‘Error Log’ snippet from the 'Variables' dropdown for the 'Email Body' which will be available once 'NotificationDeliveryFailure' is selected as the ‘Notification Type’.
...
API_Failure testStatusCode: 404, ReasonPhrase: 'Not Found', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:{ Pragma: no-cache CAMMSCulture: en-AU Cache-Control: no-cache Date: Fri, 20 Aug 2021 06:11:36 GMT Server: X-AspNet-Version: 4.0.30319 Content-Length: 264 Content-Type: application/json; charset=utf-8 Expires: -1}
Figure 3.3: SMS error notification
4. Extending permissions to link incidents with any hierarchy node |
With this feature, you will now be able to link incident records to any hierarchy node within any hierarchy, irrespective of the given view permissions in the Incident Register.
| Info |
|---|
Note: This feature is currently applicable only to customers who have enabled the new Flexible Hierarchy permission structure, which is currently in beta. |
How do you configure this?
A new permission called ‘Show Hierarchies in Links tab’ will appear under ‘Incident’ in the ‘Role Management’ area. All hierarchies created within the product will be shown under the ‘Show Hierarchies in Links tab’. Users who have access to the Role Management area can configure permissions via ' Menu > Administration > Role Management > [New icon / Edit icon of an existing role] > Product [Select Incident] > Incident > Show Hierarchies in Links Tab > [Select the hierarchies that user should see in Links tab].
...
How does this work?
If you have a hierarchy/hierarchies ticked under ‘Show Hierarchies in Links tab’ permission, within the roles you are assigned with, you will be able to see that hierarchy/hierarchies in full, within the Linkage object of an Incident record.
| Info |
|---|
Note: Although all the hierarchies are shown in the dropdown, you can only link incidents to the hierarchies you have permissions for. |
...
5. Revamped Documents and Actions tabs (objects) |
A placeholder that says “No content have been added here yet. Click “Add New” Add New to get started” will be displayed where there are no documents or actions added under the Documents and Actions tabs respectively.
...
Default sorting of records in the Document tab will be based on the 'Date Uploaded' field–beginning with newest to oldest.
6. Modifications to standard Incident Register Report |
6.1 Report content enhancements
The Incident Register report has been enhanced to include the functionalities detailed below to improve the usability of the report.
...
To help better cater for the wide variety of use cases the system is utilised for (incidents, hazards, compliant, etc.), the naming convention of the report title is now modified as below:
Where only a single incident type is selected, the report showcases the selected type as the report name.
Format: <incident type> Register Report (e.g. Hazard Register Report)
...
6. 2 Visual and layout improvements
The Incident Register Report has been updated to include the visual and layout improvements detailed below.
...