Open

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 13th July 2024 and will be available in your Live environment on 3rd August 2024.

This enhancement will introduce hierarchy node-wise permissions for Draft Records allowing users to configure permissions for Draft Records accordingly to be shown in Incident Registers. Currently, the system does not restrict records by hierarchies and nodes for Incident Draft Records, unlike Open and Closed Incident Records.

How do you configure this?

• Incident Administrators can give the permission ‘View Draft Records’ to any user role with the Product as ‘Incident’ in Mega Menu > Administration > Role Management > [User Role] > Incident > Register.  

Open

Figure 1.1: View Draft Records permission in Role Management

• Incident Administrators can give the permissions ‘Show draft records only in the linked node to the node's responsible officer’ and ‘Show draft records in linked and underlying nodes to the node's responsible officer’ to any user role in Mega Menu > Incident Settings > User Roles > [User Role] > Standard.

How does this work?

• Incident Users can see draft records in Incident Registers based on the register permissions enabled if the ‘View Draft Records’ permission is enabled along with the register permissions. 

Example: When “View Node Only” and ‘View Draft Records’ register permissions are given to a user, then the user will be able view Incident draft records linked to user’s node in every workflow as shown below. 

• Incident Users can see draft records in Incident Registers if they are responsible officer of a hierarchy node to which an Incident record is linked to if they have either of the 2 standard permissions ‘Show draft records only in the linked node to the node's responsible officer’ or ‘Show draft records in linked and underlying nodes to the node's responsible officer’

• If the user has a user role with the standard permission ‘Show draft records only in the linked node to the node's responsible officer’, then the user will be able to view draft records in Incident Registers if the user is the responsible officer of a hierarchy node to which those draft Incident records are directly linked to.

Example: When ‘Show draft records only in the linked node to the node's responsible officer’ standard permission is given to a user role given to the user, then the user will be able view draft records in Incident Registers if the user is the responsible officer of a hierarchy node to which those draft Incident records are directly linked to as shown below.

• Similarly, if the user has a user role with the standard permission ‘Show draft records in linked and underlying nodes to the node's responsible officer’, then the user will be able to view draft records in Incident Registers if the user is the responsible officer of a hierarchy node to which those draft Incident records are linked to or if the draft records are linked to a hierarchy node under that node.

This enhancement enables the Conditional Fields logic, which makes Action object fields mandatory or non-mandatory based on values of other fields in the Action Object to work also in the Action grid of the Incident Action bubble in My Quick Update.

How do you configure this?

• Incident Administrators can mark a field in a standard or custom Action Object as a conditional mandatory or Non-Mandatory field through the 'Is Conditional Field' > Mandatory/ Non-Mandatory checkbox in Incident Settings -> Object Configuration -> [Action 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 in the Action Object to work also in the Action grid of the Incident Action bubble in My Quick Update 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 in the Action grid of the Incident Action bubble in My Quick Update. Fields will become Mandatory or Non-mandatory 'on change' for newly created Action records after the condition has been defined. For action records created after the condition has been defined, the user needs to save the Incident object of the Incident record which contains the action record for the condition to be applied to the respective action record.

Before Condition is satisfied (Action Review Status shown not Mandatory)

After Condition is satisfied (Action Review Status field shown Mandatory)

This will be Phase 1 of making Camms. Risk Incident WCAG compliant. This enhancement to Camms.Incident is to meet WCAG (Web Content Accessibility Guidelines) standards, ensuring Camms.Incident product is accessible to all users, including those with special needs. This initiative aims to improve usability and inclusivity by implementing features that support accessible navigation, readability, and interaction for a seamless user experience across diverse platforms and devices.

WCAG compliance areas covered from Phase 1 are given below.

• Non-text Content

• Meaningful Sequence

• Contrast (Minimum)

• Content on Hover or Focus