Versions Compared

Old Version 1

changes.mady.by.user amani imtiyas

Saved on

compared with

New Version 2

changes.mady.by.user amani imtiyas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 11th June 2022 and will be available in your Live instance on 25th June 2022.

List of items

Table of Contents
minLevel1
maxLevel7
stylenone

1. Automatically displaying all KPIs linked to the Hierarchy

This enhancement will automatically display KPIs directly linked to a hierarchy, that the Camms.Engage Dashboard is built on, without any manual intervention.

How do you configure this?

  • A new option titled ‘KPI List/Node Component’ is added to the multi-select dropdown checkbox field labeled ‘Select the component(s) to display linked Projects, Risks, Actions and KPIs automatically’ in the Dashboard Configuration page.

  • An administrator will be able to access this option from the Dashboard Configuration page.

...

How does this work?

  • When the ‘KPI List/Node Component’ checkbox is ticked, it will ensure that going forward, all KPIs that are linked to a hierarchy 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 it will not revert the already visible KPIs.

Info

Notes:

  • This checkbox will not impact the KPIs that are already linked to a hierarchy. Only the KPIs that are linked subsequent to activating this setting, will be automatically linked.

  • This enhancement will only be applicable for KPIs that are directly linked to a hierarchy. If the KPIs are added as sub-components such as ‘Project KPIs’ and ‘Sub KPIs’, then these would not be made visible automatically, but would require manual user intervention.

2. Automatically displaying all Actions inked to the Hierarchy

This enhancement will automatically display Actions directly linked to a hierarchy, that the Camms.Engage Dashboard is built on, without any manual intervention.

How do you configure this?

  • A new option titled ‘Action List/Node Component’ is added to the multi-select dropdown checkbox field labeled ‘Select the component(s) to display linked Projects, Risks, Actions and KPIs automatically’ in the Dashboard Configuration page.

  • An administrator will be able to access this option from the Dashboard Configuration page.

...

How does this work?

  • When the ‘Action List/Node Component’ checkbox is ticked, it will ensure that going forward, all Actions that are linked to a hierarchy, that 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 will not revert the already visible actions.

Info

Note: This checkbox will not impact the actions that are already linked to a hierarchy. Only Actions that are linked subsequent to activating this setting, will be automatically linked.

3. Enhancing the Project Template to be compatible with Common Components

This enhancement will let you apply detail level common component configurations of the selected template, to all Projects within the Camms.Engage Dashboard.

How do you configure this?

  • Once the ‘Template Project’ functionality is activated from the Dashboard Creation/Edit page, the option of choosing a Template Project will be provided in all Project List/Node components.

...

  • Once a Project is selected as a template, a validation message will be displayed in a popup window. Apart from the standard template functionality, the validation message will now have a new option.

  • This new option will let you make a selection to apply the template functionality for all detailed level common components that are placed and configured against the selected project.

...

How does this work?

The following actions will take place upon confirmation:

  • Any detail level common component available within the template project, will be copied over to the projects that will be made visible automatically or manually.

Example: If the ‘Image Gallery’ component is configured for the template project, going forward, all projects that will be linked to a hierarchy and enabled within Camms.Engage via the Project List or Project Node, will inherit the same ‘Image Gallery’ component and its configurations, without any user intervention.

...

  • This will not be applied to projects that are made visible prior to selecting a template project.

Info

Notes:

  • This will only be applicable to projects that will be made visible subsequent to selecting the Template Project.

  • Changing the visibility of the Template Project, will not have an impact on the Template Project’s common component configurations or the existing configured project’s settings.

  • If there is a project with visibility switched off after few days of activation, and later, the visibility is switched back on, that project will not inherit the common component configurations of the new project template, but will have the previous configurations.

4. Enhancing the Risk Template to be compatible with Common Components

This enhancement will let you apply detail level common component configurations of the selected template, to all Risks within the Camms.Engage Dashboard.

How do you configure this?

  • Once the ‘Template Risk’ functionality is activated from the Dashboard Creation/Edit page, the option of choosing a Template Risk will be provided in all Risk List/Node components.

...

  • Once a Risk is selected as a template, a validation message will be displayed in a popup window. Apart from the standard template functionality, the validation message will now have a new option.

  • This new option will let you make a selection to apply the template functionality for all detailed level common components that have been placed and configured against the selected risk.

...

How does this work?

The following actions will take place upon confirmation:

  • Any detail level common component available within the Template Risk, will be copied over to the risks that will be made visible automatically or manually.

Example: If the ‘Rich Text Editor’ component is configured for the Template Risk, going forward, all risks that will be linked to a hierarchy and enabled within Camms.Engage via the Risk List or Risk Node, will inherit the same ‘Rich Text Editor’ component and its configurations without any user intervention.

...

  • This will not be applied to the risks that are made visible prior to selecting a Template Risk.

Info

Notes:

  • This will only be applicable to risks that 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 common component configurations or the existing configured risk’s settings.

  • If there is a risk with visibility switched off after few days of activation, and later, the visibility is switched back on, that risk will not inherit the common component configurations of the new Risk Template, but will have the previous configurations.

5. Introducing Rollup Action Linkages in the Action List component

This enhancement will let you showcase values for Rollup Action linkages under the Action List component. This can be configured by an administrator and then be displayed to users.

How do you configure this?

  • In the Dashboard Admin panel, a new list field will be available under the Configuration Menu, titled ‘Rollup Action Linkages’.

  • An administrator can tick the 'visibility' checkbox and configure the label name to capture the field into the Dashboard.

...

How does this work?

  • If the visibility checkbox is ticked, and ‘Rollup Actions’ are activated from the ‘Edit’ menu of the Action List component, the ‘Rollup Action Linkages' values will be captured into the Dashboard.

Example: If hierarchy node A has three child levels X, Y and Z, with linked Actions, and if an Action List is placed against node A, these actions linked to child levels will be identified as Rollup Actions. Therefore, this modification will show you the original linked hierarchy node(s) of these Actions.

...

  • If the visibility checkbox is unticked, the 'Rollup Action Linkages' field will not be captured into the Dashboard. 

Info

Notes: 

  • If the field visibility is switched ON from the admin panel, but the Rollup Actions are not activated from the Action List configurations, then the field visibility will be hidden from the Dashboard. 

  • An 'info' icon will be displayed in front of the field to provide more clarity to the user with a message ‘This field will show you the linkages of the roll-up actions. Therefore, this field will be visible only if the action list is configured to show Roll-up Actions’.

  • The new 'Rollup Action Linkages' field will be compatible with all Dashboard refresh options, Dashboard copying, and all other standard Dashboard functionalities.

...