cammsrisk | December Feature Release Note
- amani imtiyas (Unlicensed)
1. Ability to mitigate multiple risks using the same risk action |
Ability to mitigate multiple risks using the same risk action is now introduced within cammsrisk, where risk actions can be maintained commonly and linked to multiple risks to be parallally managed.
This can be enabled via the setting ‘Enable Risk Actions to be managed commonly’ accessed via Cammsrisk > Administration > Configuration > Settings area which will be ‘OFF’ by default.
When this setting is enabled, the risk actions will be converted to be common, and users will be able to link the same risk action to multiple risks where applicable and manage them commonly as well.
When the setting is ON;
Below the risk action grid/s in the risk assessment pages, there will be a new option titled ‘Select Existing Solutions’ upon clicking, a pop-up appears showing the listing of all available risk actions.
Users will be able to select an existing action from the pop-up, or add a new action by the inline add option to the risk.
Figure 1.3: The pop up listing all risk actions in the system
The pop-up will comprise of filters to further help users to search and filter for the actions to link as well. Filters to search for risk actions by common attributes such as Title, Start and End dates, Status, Responsible officer and the Business unit with which it is linked to - will be available here.
When this setting is ON, if the same action is linked to multiple risks as above, any update to any of the fields of the action will be commonly managed hence the updates will flow across to all risks with which the action is linked to.
Example:
If you have linked an action to 5 risks and update the action’s status from within the risk to be from ‘In progress’ to ‘Completed’, this change will be reflected across all 5 risks with which that action is linked to. This will be the same behaviour for all fields for the risk action.
Risk action details screen, accessed by clicking on the title of the risk action, and the ‘My Risk Actions’ section in the quick update is further improved to show a table of all risks linked with a common action as such as well.
Important Notes:
We are working on enhancing the ‘My Risks’ section in the quick update to remove the existing grouping by the risk type and have actions commonly available via a future sprint. The risk type name will be hidden for now and the existing segregation too will be removed in the future via an update to the feature.
The ‘Quick Action Search’ area will only list a commonly linked action under the first risk with which it was linked/created through. We will be addressing in the future as a part of the roadmap enhancement to the Quick action search area.
If you also have cammsinsights;
If you decide to enable this feature, please note that your Risk_RiskSolutionDetails_STND dataset within cammsinsights can end up depicting a larger number of rows since a single action linked to two risks will appear twice.
Please ensure report design takes this into account and adjust your existing reports accordingly.
Example: If attempting to count unique actions, always use the Count Distinct option within cammsinsights.
2. Ability to enforce hierarchy linkages as mandatory when creating new risks and incidents |
Administrators will be able to define having linkages to certain hierarchies (based on preferred hierarchies configured) as mandatory when a user created a risk or an incident.
Note: This feature will only be applicable for clients with the flexible hierarchy structure enabled in the database.
A new setting ‘Select Mandatory Hierarchies for Risk/Incident Creation’ is available for the Administrators in the Settings area, accessed via cammsrisk > Administration > Configuration where they can choose to set up a condition whereby its mandatory for users to have at-least one linkage with the set up hierarchies in order to add a risk/incident into the system.
The options for selection are the Organisation hierarchy and any custom hierarchies in the system. Planning hierarchy will also be introduced as a part of a future sprint release.
When the necessary configurations are done and saved, whenever a user is attempting to add a risk/incident, the system will mandate the addition of these hierarchy linkages as well.
Note: Since this is mandated during the risk/incident creation process, ensure that your configurations need to have the ‘Add/Edit Links’ options enabled in the first pages of record creation to allow users to add linkages at the point of creating the records.
Please contact CAMMS Support if you wish to get our help further on this.
3. Ability to auto populate risk or incident creator's individual hierarchy linkage as default |
This feature will provide the option where the hierarchy that a user is linked to is automatically added to the risks or incidents they are creating.
Note: This feature will only be applicable for clients with the flexible hierarchy structure (which is currently in limited release) enabled in the database.
A new setting ‘Auto Populate Risk/Incident Creator's Hierarchy Linkages As Default Risk/Incident Linkages Upon Creation’ is available for the Administrators in the Settings area, accessed via Cammsrisk > Administration > Configuration, upon enabling which the individual hierarchy linkages a user has, will be auto populated in to the risk/incident when they are adding them.
The users have the flexibility to delete the auto populated linkages if necessary as well.