Camms.Insights | December 2021
- amani imtiyas
Camms is pleased to bring you the Quarterly Product Release Note for Camms.Insights.
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 4th December 2021 and will be available in your Live instance on 18th December 2021.
Camms.Risk
1. Introducing a risk aggregation capability to Camms.Insights datasets |
This enhancement will relate to the Camms.Risk feature release 'Aggregating risks across the enterprise', and will reflect on the Insights Risk Assessment datasets mentioned below:
Risk_StrategicRiskInitial_STNDÂ
Risk_OperationalRiskInitial_STNDÂ
Risk_CorporateRiskInitial_STNDÂ
Risk_ProjectRiskInitial_STNDÂ
Risk_StrategicRiskRevised_STNDÂ
Risk_OperationalRiskRevised_STNDÂ
Risk_CorporateRiskRevised_STNDÂ
Risk_ProjectRiskRevised_STNDÂ
Risk_StrategicRiskFuture_STNDÂ
Risk_OperationalRiskFuture_STNDÂ
Risk_CorporateRiskFuture_STNDÂ
Risk_ProjectRiskFuture_STNDÂ
The following fields are introduced to the above existing datasets:
Field Name | Data Type | Remarks |
|---|---|---|
PARENTRISKID   | Text | This is a unique identifier for each parent risk and can be used to link with other datasets |
Parent Risk Title | Text | Title of the parent risk |
Parent Risk Code | Text | Reference number of the parent risk |
Parent Risk Rating Score   | Numeric | Risk rating score of the parent risk (e.g. 18, 21) |
Parent Risk Rating Description | Text | Risk rating description of the parent risk (e.g. High, Low) |
Aggregate Risk Score | Numeric | Risk rating score of the aggregate risk (e.g. 18, 21) |
Aggregate Risk Description  | Text | Risk rating description of the aggregate risk (e.g. High, Low) |
Following are some sample data included in the dataset:
Parent Risk Code | Parent Risk Title | Parent Risk Rating Score | Parent Risk Rating Description | Aggregate Risk Score Aggregate Risk Score | Aggregate Risk Description |
|---|---|---|---|---|---|
RSK-22 | Loss of critical information | 32 | High | 53 | High |
RSK-41 | Failure to comply with regulatory requirements | 18 | Low | 26 | Medium |
RSK-74 | Unauthorised access to system data | 24 | Medium | 35 | High |
RSK-101 | Inability to retain staff | 11 | Low | 23 | Low |
2. Introducing a new dataset for Compliance and Policy hierarchy linkages |
This Compliance_CompliancePolicyFlexOrgHierarchyLink_STND dataset will present how a policy record in the Camms.Risk Compliance product is linked to the different levels of your Flexible Organisation Hierarchy. This will help filter policies based on a selected hierarchy node.
Note:Â This feature is currently applicable only to customers who have enabled the new Flexible Hierarchy permission structure, which is currently in beta.
The following fields are included in the dataset:
Field Name | Data Type | Remarks |
|---|---|---|
POLICYIDÂ | Text | This is a unique identifier for each policy and can be used to connect with other datasets |
Policy Title | Text | The name of the policy |
HIERARCHYID | Text | Unique ID of the Hierarchy that can be used to link with other related datasets |
HIERARCHYLEVELID | Text | Unique ID of the Hierarchy Level that can be used to link with other related datasets |
HIERARCHYNODEID | Text | Unique ID of the Hierarchy Node that can be used to link with other related datasets |
Hierarchy Name | Text | Captures the name of the Hierarchy that the policy is linked to (e.g. Organisation Hierarchy) |
Hierarchy Level | Text | Captures the level of the Hierarchy the policy is linked to (e.g. Business Unit) |
Hierarchy Node Name | Text | Captures the Hierarchy Node the policy is linked to (e.g. Corporate Services) |
Following are some sample data included in the dataset:
Policy Title | Hierarchy Name | Hierarchy Level | Hierarchy Node Name |
|---|---|---|---|
Legal and Regulatory Compliance Policy | Compliance Framework | Unit | Legal & General |
Personal Information Policy | Organisation Hierarchy | Section | HR Services |
Electronic Devices and Services Policy | Infrastructure Hierarchy | Section | IT Services |
Copyright Compliance | Compliance Framework | Unit | Legal & General |
The below table shows you the default relationship which you can set up as a System Administrator:
Join Type | Data Object | Join Field | Â | Foreign Data Object | Join Field |
|---|---|---|---|---|---|
INNER | Compliance_CompliancePolicyDetails_STND | POLICYID | = | Compliance_CompliancePolicyFlexOrgHierarchyLink_STND | POLICYID |
To ensure this new dataset is enabled for use within your Camms.Insights application, please click the link below or copy and paste the link into your web browser and follow the steps:
Camms.Project
3. Modifying the task related datasets in Camms.Project |
With this feature, the IsMilestone field which was added to the Project_TaskDetails_STND dataset, will be incorporated to the Project_TaskDetailsCurrentPhase_STND and Project_TaskDetailsAll_STND datasets. The field will return a yes or no value. This will be based on the existing field, 'Duration' in the same dataset and if the task duration is 0, then it will be considered as a milestone.
4. Introducing a new dataset to return project board and team data from the current phase |
With the introduction of this new Project_BoardAndTeamCurrentPhase_STND dataset, details of the Project Board and Team object will be captured, which is in the current or the latest phase (In the absence of current phase data) of the project. The fields that should be available for the dataset will be enabled through the Field Visibility checkboxes in Object Configuration under Project Workflow.
The below table shows you the default relationship which you can set up as a System Administrator:
Join Type | Data Object | Join Field |
| Foreign Data Object | Join Field |
INNER |  Project_BoardAndTeamCurrentPhase_STND  | PROJECTID | = |  Project_ProjectRegister_STND  | PROJECTID |
To ensure this new dataset is enabled for use within your Camms.Insights application, please click the link below or copy and paste the link into your web browser and follow the steps:
5. Introducing additional custom list fields to Project datasets |
With the enhancement to the Details object in Camms.Project, five (5) new Custom List fields will be introduced to the following datasets upon configuring as below.
Project_ProjectDetails_STND: Will be available in the dataset once activated from the object configuration area of the Project Details object.Â
Project_ProjectRegister_STND: Will be available in the dataset once activated from the Project Register View page.Â
Project_QuickUpdate_STND: Will be available in the dataset once the visibility is activated (Field Visible in Quick Update tick box is ticked) from the object configuration area of the Project Details object.
To ensure these new fields are enabled for use within your Camms.Insights application, please click the link below or copy and paste the link into your web browser and follow the steps:
6. Introducing new Budget fields to Project Register dataset |
With the enhancement to the Implementation Budget object in Camms.Project, following new budget fields will be introduced to the Project_ProjectRegister_STND dataset, allowing users to view budget data. Â The fields can be made available to the dataset by enabling the visibility via the Project Register View under Project Settings in Camms.Project.
Net Budget YTD
Net Actual YTD
Budget Variance
Budget Variance %
Current Year Budget Status
To ensure these new fields are enabled for use within your Camms.Insights application, please click the link below or copy and paste the link into your web browser and follow the steps:
Â