Camms is pleased to bring you the Product Update Release Note for Camms.Risk Incident Capability.
In this release we've got exciting enhancements to improve your user experience within the system, which will be available in both your Test and Live environments on the following dates:
United Kingdom / North America / Middle East - Wednesday, 10th April.
Australia / Asia - Thursday 11th April.
------------------------------------------------------------------------------------------------------------------------------------------
Introduction of Conditional fields in Incident workflows (Phase 2 – Conditional fields for incident creation)
This modification allows us to configure conditional fields within Incident workflows, enabling the ‘Show’ and ‘Hide’ functionality of fields for Incident creation based on conditions defined based on values defined in other fields.
How do you configure this?
- Incident Administrators can now mark a field as a conditional field through the already introduced 'Is Conditional Field' setting 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 'Show Field,' and 'Hide Field’.
Figure 1.1: Conditional Mode Settings in Field Configuration Details
- Incident Administrators can define conditions to show or hide a field based on values of other fields on incident creation from field value configuration area in Incident Settings -> Field Value Configuration.
Figure 1.2: Field Value Configuration area
How does this work?
- Incident Users can now experience conditional field visibility based on given values in other fields during Incident creation as well. Fields will be shown or hidden 'on change' of other fields in the Incident Object.
During Incident Creation before Condition is satisfied
Figure 1.3: Before value change on ‘Action Required’ field
During Incident Creation after Condition is satisfied
Figure 1.4: After value change on ‘Action Required’ field.
After Incident Creation
Figure 1.4: After Incident Creation