Camms is pleased to bring you the Quarterly Product Update Release Note 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 12th October 2024 and will be available in your Live environment on 2nd November 2024.

This modification introduces the linking of KPIs to Incident records using field-wise linkage and the linkage object.

How do you configure this?

• Incident Administrators can grant KPI View permissions to any user role via Mega menu > Administration > Role management > [Role] > [CAMMSTRATEGY] > Planning > Performance management > KPIs > View > [View Permission(s)]

• Once permissions are set, users will see the ‘KPI’ option in the ‘Linkage Types’ dropdown within the Incident record Linkage Object.

How does this work?

• Users will be able to link KPIs to Incident records via both linkage object and field wise linkage buttons from the available KPIs, which are displayed based on their KPI View permissions.

• The linked KPI will appear as a hyperlink, allowing users to navigate directly to the KPI record.

• Additionally, linked KPIs will be tracked in the audit history of the Linkage Object, showing details such as the user responsible for the linkage, timestamp, and summary of the linkage.

This enhancement will provide users with the ability to make group header fields visible or not visible 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 group header type field as a conditional hide or show field through the 'Is Conditional Field' > Show/ Hide 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 'Show Field' and 'Hide Field’.

• Incident Administrators can define conditions to make visible or non-visible a group header type 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 visible and Non-visible fields based on given values in other fields. Fields will be hidden or shown '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. Conditions will be applicable to all the other type fields falls under the conditional group header field.

Before Condition is satisfied (Group header field is not shown)

After Condition is satisfied (Group header field is shown)

This modification reverts the values of a conditional field to null or to the default value when the field value(s) is changed or when the condition is unsatisfied.

How does this work?

• This will revert the value of a conditional field to null or to the default value when the field value(s) is changed which satisfied a conditional criteria of a conditional show field and the condition is unsatisfied. Additionally, users will receive a warning message on change when a value of a conditional field is getting wiped off. This will enhance user experience and prevent confusion.

Example: 'Impact and causes' group header will be shown, if the Incident Severity is Moderate.

Group header field and all the fields within the group header are shown since the condition is satisfied.

If the user tries to un-satisfy the condition, below warning message will be shown on change.

• In the above warning message, if the user clicks the ‘OK’ button, the value of conditionally dependent field(s) will be wiped off. If the user clicks the ‘Cancel’ button, then the value of the conditionally dependent field(s) will not be wiped off and the changed value of the field which used to un-satisfy the conditional criteria will be reverted back to the previous value which satisfied the conditional criteria.

This modification introduces 'Action Creator' as a notification snippet in Notification Templates when the notification type is 'Action.

How do you configure this?

• Incident Administrators will be able to utilize newly introduced [ActionCreator] snippet from the variable dropdown in Incident Settings -> Notification Templates when the notification type is ‘Action’ as shown below.

How does this work?

• Incident Users will be able to receive notifications configured with the newly introduced [ActionCreator] snippet for notification type “Action”, based on the notification criteria and notification template.

This enhancement aims to allow users to show or hide the getting started page in LHS and Mega-Menu based on newly introduced role management permission in the Camms.Incident product.

How do you configure this?

• Incident Administrators can give the permission ‘Getting Started’ to any user role with the Product as ‘Incident’ in Mega Menu > Administration > Role Management > [User Role] > [INCIDENT] > Workspace > Getting Started.  

How does this work?

• Incident Users will see the getting started page in both LHS bar (Left Hand Side navigation menu) and Mega menu only if that user has ‘Getting Started’ permission.

• If a user without the ‘Getting Started’ permission attempts to access the Getting Started page by entering the URL, they will see the below no permission screen.

​This modification would enhance the Incident Master Report to capture linked KPIs within the Report.

How does this work? 

• This modification would specifically enhance the ‘Linkage’ section of the report, where a new ‘Link Type’ called ‘KPI’ has been introduced.

• The ‘Link Name’ column under the Linkage table will now allow you to see a list of KPIs that has been linked to the Incident Record that the Report was generated for.