Camms.Risk Incident Management - May 2024
- amani imtiyas
Camms is pleased to bring you the Quarterly Product Update Notification for the Camms.Risk Incident Capability
This quarter we've got exciting enhancements to improve your user experience within the system, which will be available in your Test environment on 29 April 2024 and will be available in your Live environment on 20th May 2024.
1. Introduction of Conditional fields in Incident workflows [Phase 2] |
|---|
This enhancement will provide users with the ability to make fields mandatory or non-mandatory in selected workflows based on specified conditions. These conditions can be based on values of other fields, both during and after incident creation.
How do you configure this?
Incident Administrators can now mark a field as a conditional mandatory or Non-Mandatory field through the 'Is Conditional Field' > Mandatory/ Non-Mandatory checkbox in Incident Settings -> Object Configuration -> [Object] -> Field Configuration Details.
Fields will be displayed in the 'Field Value Configuration' area based on the Conditional Mode setting options 'Mandatory,' and 'Non-Mandatory’.
Incident Administrators can define conditions to make mandatory or non-mandatory a field based on values of other fields during incident creation as well as after the incident creation from field value configuration area in Incident Settings -> Field Value Configuration.
How does this work?
Incident Users can experience conditional Mandatory and Non-Mandatory fields based on given values in other fields. Fields will become Mandatory or Non-mandatory 'on change' in the same object as well as after the relevant object is successfully saved if it is in different objects when the given condition is satisfied. Conditions can be altered, and fields can be filled based on the sequence and conditions.
Before Condition is satisfied (Severity field shown not Mandatory)
After Condition is satisfied (Severity field shown Mandatory)
Note: Incident Users can now experience conditional Show/Hide and Mandatory/Non-Mandatory fields in Incident Action Object as well. But conditional fields in the Action object will work only for conditions defined based on fields in the same object.
2. Enhancement to the signoff feature by introducing Sequential and Concurrent signoff (Phase 1) |
|---|
This enhancement will introduce concurrent and sequential sign-off processes to the Camms Incident workflows.
How do you configure this?
Incident administrators can now enable newly introduced 'Concurrent' and 'Sequential' signoff options via Incident Settings -> Object Configuration -> [Sign off Enabled Object] -> Object Configuration Details.
Incident administrators can now chose either ‘At least one approval needed’ or ‘All approvals needed’ for Concurrent Sign off option.
By default ‘Concurrent’ and ‘At least one approval needed’ will show selected and user can change the configurations as required.
Incident administrators can now enable newly introduced ‘Sync Selected Values to Signoff Authority by Default’ setting via Incident Settings -> Object Configuration -> [Object] -> Field Configuration settings to all fields with field type ‘Staff Dropdown’ and ‘Staff Multi Select’
Incident Administrators can give newly introduced standard permission ‘Standard Incident Signoff Delegated Approver permission’ to users via Incident Settings -> User Roles.
Incident Administrators will be able to select both Type and Object when configuring notifications for 'Sign Off' type notifications via Incident Settings -> Notifications
Incident administrators will be able to utilize reassign staff responsibilities page to reassign ‘Incident Signoff Authority’ related responsibilities.
How does this work?
When ‘Enable Sign Off’ is ticked for an object, it will expose new options for Sequential and Concurrent Sign Offs as radio button selection option.
It is quite flexible to configure a sign off type per object. If Sequential sign off is selected, then the sign-offs will follow a sequential approach, alternatively, if Concurrent sign off is selected the system will expose two new options for concurrent sign off as ‘At least one approval needed’ or ‘All approvals needed’.
If the ‘Sync Selected Values to Signoff Authority by Default’ setting is enabled for a ‘Staff Dropdown’ or ‘Staff Multi Select’ type field, then selected values of that field will be synced to Sign off Authority field as shown below.
Once the Sign Off is submitted, users will be able to approve, reject or reverse the Sign off from both the respective object where the sign off is configured and My quick update.
Incident users will be able to receive email notifications when a signoff is submitted, rejected and approved.
Note: MOC Signoff Enhancement (Phase 1) is just around the corner and will be available from the Demo Release on May 10th, 2024. Please note that there is an identified issue when Signoff is submitted for existing incidents, the record is shown to be submitted again. This will be fixed by next week before the live release.
3. Introduce the snippet ‘[LinkedHierarchyNodes]’ to show when the Notification Type is ‘Risk’. |
|---|