Camms is pleased to bring you the Quarterly Product Release Note for Camms.Engage.

This quarter we've got a number of exciting new features and enhancements to improve your user experience within the system, which will be available in your Test environment on 12th March 2022 and will be available in your Live instance on 26th March 2022.


List of items

1. Automatically displaying all risks which are linked to the hierarchy

2. Enhancement to the Risk List and Risk Node components to display the template status

3. Automatically displaying all projects linked to the hierarchy within the Project Phase Summary extended component

4. Showcasing Obligation details in Camms.Risk Compliance within Camms.Engage

5. Customising the sequence of columns in the Risk and Risk Heatmap details components

6. Risk Control List, Risk Control Node, and Risk Control Details to be compatible with the new Control Register module


1. Automatically displaying all risks which are linked to the hierarchy

This enhancement will allow the Administrator to ensure that any risks that are directly linked to a hierarchy, which the Camms.Engage dashboard is built on, would automatically be displayed without any manual intervention.

How do you configure this?

  • A new option titled ‘Risk List/Node Component’ is added to the multi-select dropdown checkbox field labeled ‘Select the component(s) to display linked projects and risks automatically’ in the dashboard Configuration page.
  • An administrator will be able to see this checkbox once navigated to the Configuration page.

Figure 1: Dashboard configuration section for risk auto linkage

How will this work?

  • When the checkbox is ticked, it will ensure that going forward all the risks which are linked to a hierarchy, which the dashboard is based on, will be made visible and displayed automatically. 
  • An administrator will have the option to tick or untick this checkbox at any given time. However, unticking would not revert the already visible risks.

Notes:

  • This checkbox will not impact the risks which are already linked to a hierarchy. Only the risks which are linked subsequent to activating this setting will be automatically linked.
  • Additionally, in order for the risk auto linkage functionality to apply its changes across the database, all users logged into Camms.Engage and Camms.Risk products at the time the setting will be switched ON, will require to log out of the system and then log back into the relevant application once the setting is enabled.


2. Enhancement to the Risk List and Risk Node components to display the template status

This enhancement will let you select a template risk with the detail level configuration which should be applied to all the other risks within the dashboard.

How do you configure this?

  • A checkbox titled ‘Enable Template Risk’ will be available in the edit section of the dashboard.

Figure 2.1: Dashboard configuration section for risk template

  • Once the checkbox is ticked, the option of choosing a template risk will be provided in all Risk List/Node components.
  • This will be a radio button, where only a single risk can be selected at any given time representing all Risk Lists and Risk Nodes placed within the dashboard.

Figure 2.2: Selection of a risk template via admin panel

  • Upon selecting a risk as template, a validation message will be displayed as a popup.

Figure 2.3: Template risk confirmation popup


How will this work?

The following actions will take place upon confirmation:

  • Going forward, any detail level component available within the template risk, will be copied over to the risks which will be made visible automatically or manually.
    For instance, if the risk detail component is configured for the template risk, going forward, all the risks that will be linked to a hierarchy and enabled within Engage via the Risk List or Risk Node, will inherit the same risk detail component without any user intervention.
  • This will not be applied to the risks which are made visible prior to selecting a template risk.
  • If the checkbox is ticked as depicted below, all the Risk Controls which are in the risk detail level will automatically be made visible.

Figure 2.4: Enabling risk controls with template risk

  • This is only applicable for the Risk Controls which have been linked to the risks at the instance of making the risk visible. Any Risk Controls linked to the risk in the future will not be automatically made visible.
  • In the case where the default risk has no detail level components, a popup message will be displayed for confirmation.

Figure 2.5: Template risk confirmation popup for no detail components


Notes:

  • This will only be applicable to risks which will be made visible subsequent to selecting the template risk.
  • Changing the visibility of the Template Risk, will not have an impact on the Template Risk’s configurations or the existing configured Risk’s settings.
  • In case if there has been a risk with visibility switched off after few days of activation, and then visibility is switched back on, that risk will not inherit the configurations of the new risk template but will have the previous configurations.
  • If the Risk that was set as the Template Risk, is deleted from Camms.Risk or if the Risk List/Node component containing the Template Risk has been deleted from Camms.Engage, a message stating that ‘Template risk has been deleted.’ will be shown within the remaining Risk Lists and Node components.


3. Automatically displaying all projects linked to the hierarchy within the Project Phase Summary extended component

This enhancement will let an administrator ensure that any projects that are directly linked to a hierarchy which the Camms.Engage dashboard is built on, would automatically be displayed within the Project Phase Summary Extended component without any manual intervention.

How do you configure this?

  • A new option titled ‘Project Phase Summary Extended Component’ has now been added to the multi-select dropdown checkbox field labeled ‘Select the component(s) to display linked projects and risks automatically’ in the Dashboard configuration page.
  • An administrator will be able to see this checkbox once navigated to the Configuration page.

Figure 3: Dashboard configuration section for project phase summary extended component's auto-linkage

How will this work?

  • When the checkbox is ticked, it will ensure that going forward, all projects which are linked to a hierarchy the dashboard is based on, will be made visible and displayed automatically within the Project Phase Summary Extended component.
  • An administrator will have the option to tick or untick this checkbox at any given time. However, unticking will not revert the already visible projects.

Note: This checkbox will not impact the projects which are already linked to the hierarchy. Only the projects which are linked subsequent to activating this setting, will be automatically linked.


4. Showcasing Obligation details in Camms.Risk Compliance within Camms.Engage

With the new Obligation Detail component, you can now showcase a detailed view of any obligation in the Camms.Engage Dashboard.

How do you configure this?

  • When you drilldown into an Obligation from the Admin Panel via the Obligation Summary component, a new detail level component titled ‘Obligation Detail’ will be available under Dashboard components in the ‘COMPLIANCE’ section.

Figure 4.1: Obligation detail component placement

  • Dragging and dropping the Obligation Detail component will then let you configure the detailed view of the selected Obligation, where it will enable an administrator to configure the preferred field(s) to be shown within the Dashboard.
  • The sequence of the fields can be changed as well, wherein the preferred order of fields set within the configuration menu will reflect within the Dashboard.

Figure 4.2: Obligation detail component field configuration

  • If you need to add the Obligation Detail component to all the Obligations within its parent component ‘Obligation Summary’, you can select the ‘Add to all Obligations’ button from the edit menu of the Obligation Detail component.

Figure 4.3: Add to all obligations feature

How will this work?

  • Once you click on a particular Obligation record from the Obligation Summary grid, the entire popup window will navigate to the Obligation Detail component, by hiding the existing screen, with Authority Document details and Obligation Summary grid values.

Figure 4.4: Selection of the obligation via obligation summery component


Figure 4.5: Dashboard view of obligation detail component

  • A breadcrumb will be activated at the top of the component to showcase the navigation and current position. Wherein, the title of the popup will be updated as the breadcrumb.

Figure 4.6: Updated breadcrumb with navigation


Notes:

  • ‘Obligation Description’ and ‘Review Comments’ fields are excluded from the above sequencing, wherein even if the sequence is changed, the field placement would remain static on the dashboard.
    • Obligation Description will be shown as the top-most field, wherein Review Comments will be shown as the last field at the bottom of the component.


5. Customising the sequence of columns in the Risk and Risk Heatmap details components

This enhancement will let an administrator arrange the field order of the Risk Detail component by simply dragging and dropping the fields.

The grid displayed in the dashboard will then reflect the sequence set from the admin panel.

How do you configure this?

  • When you navigate into the configuration menu of the Risk Detail component, you could change the field placements by simply dragging and dropping the fields based on your preferred order.

Figure 5.1: Default field placement of risk code within the risk detail component


Figure 5.2: Updated field placement of risk code within the risk detail component


How will this work?

  • The sequence that you have set within the Admin Panel, will be reflected in the Dashboard.

Figure 5.3: Dashboard view of the default field placement of risk code


Figure 5.4: Dashboard view of the updated field placement of risk code


Notes: 

  • ‘Risk Owner Comments’ and ‘Management Comments’ fields are excluded from the above sequence ordering modification, wherein even if the sequence is changed from the admin panel, the field placement would remain static in the dashboard.
  • With this new enhancement, the existing static field order will be changed to be equivalent to the field order of the admin panel.


6. Risk Control List, Risk Control Node, and Risk Control Details to be compatible with the new Control Register module

With the introduction of the revamped Controls Register, you can now showcase these new Controls that are linked directly to the Hierarchies, along with the Controls that are linked to the Risks.

How do you configure this?

  • The existing Risk Control List, Node, and Detail component names and their positioning have been updated to provide more clarity and to make it easier to configure Controls within Camms.Engage.

  • Consequently, the ‘Control List’, ‘Control Node’ and ‘Control Detail’ components are listed down within a new section under Dashboard Components in the Admin Panel, titled ‘CONTROL’.

Figure 6.1: Admin panel control list and node placement


Figure 6.2: Admin panel control detail placement

  • In addition to the existing Risk Control component functionalities, the new Control List and Node components will now let you select between the option of showing all risk related controls within the Control components or showcase Controls that are directly linked to the hierarchy based on where the component is placed.

Figure 6.3: Control list view of directly linked and risk related control selection


Figure 6.4: Control node view of directly linked and risk related control selection


How will this work?

  • If the visibility checkbox is ticked, the selected ‘Controls' will be displayed in the dashboard, along with the field configurations.

Figure 6.5: Dashboard view of control list

Figure 6.6: Dashboard view of control node

Figure 6.7: Dashboard view of control detail


Note: This new functionality will be available for the control components added as a main component into a hierarchy node only. If the control components are added as detail components, the above functionality will not be available.