Camms is pleased to announce the December Feature Release for Camms.Risk Incident Management.
This was released on 12th December 2020 and includes the following new features and enhancements to improve your user experience within the system.
1. Notify users via email/SMS during API request failures
A new notification type will be introduced to notify pre-defined users about API request delivery failures via SMS or Email. This includes the ability to specify the number of retry attempts as well as the duration between retries.
How to configure it?
1.1 Template Creation
A Notification Type named ‘Notification Delivery Failure’ will be available under Notification Templates, accessed via Menu > Incident Settings > Notification Templates.
Select ‘NotificationDeliveryFailure’ from the Notification Type dropdown and tick the Notification Methods as ‘Email’ and ‘SMS’. The ‘Error Log’ snippet will be available to be selected from the Variables dropdown in the Email/SMS Body, when drafting the email/SMS template.
The Error Log snippet will include the Error Log which was produced when the exception occurred.
1.2 Notification Creation
When ‘NotificationDeliveryFailure’ is selected as the Notification Type, when creating a notification via Menu > Framework > Incident Settings, a new trigger criteria ‘Notify Upon Delivery Failure’ will be available.
When ‘Notify Upon Delivery Failure’ is selected as the trigger criteria, the ‘Custom Trigger Criteria Configurations’ editor will be displayed.
Notation for the retry attempts should be entered in the editor in the below form:
iif([success] ='<error code>,'{SEND}','{RETRY(<duration>,<retrycount>)}')
The duration requires to be entered using integer numbers and the minimum value will be 0. The unit for the duration is hours.
Once 0 has been entered as the duration, then the Retry Attempts will occur continuously.
You can add external parties as recipients using the Additional Recipient/s field.
1.3 Linking the Failure Notification to an API Request
A dropdown named ‘Failure Notification’ will be introduced in the API request created.
You can link the failure notification using this dropdown.
2. Updates to Standard Incident Reports
2.1 Incorporating new Camms branding into the report
The cover pages of the 'Incident Summary Report' and 'Incident Master Report' have been updated to include the new Camms logo and branding.
2.2 Updates to Incident Status Overview Chart
The ‘Incident Status Overview’ chart within the Incident Summary Report has been updated to include the details below.
The chart has been modified to capture all incident statuses along with its relevant ‘value level colour’ configured within the application.
Incident statuses can be configured within the application using the below navigation path:
Menu > Incident Settings > Lists > CloseIncidentStatus.
The ‘value level colour’ of an incident status can be configured within the application using the below navigation path: Menu > Incident Settings > Lists > CloseIncidentStatus > Select an option (name) > Choose Value Level Colour (field’s colour).
Note: ‘Incident status value level colour’ of the statuses will pick a random colour(s) if a relevant colour(s) have not been configured within the application.
2.3 Visual and Layout Improvements
The Incident Master Report has been updated to include the visual and layout improvements detailed below.
The appearance of the incident action performance traffic light icons within the incident action summary grid has been improved to allow clear visualisation of information.
The Incident Summary Report has been updated to include the visual and layout improvements detailed below.
The appearance of the ‘Incident Status Overview’ chart has been improved to allow clear visualisation of information.
Note: All changes mentioned above related to the Incident Master Report has only been updated for the default orientation report type (landscape).
