...
Camms is pleased to bring you the Quarterly Product Release Note for Camms.Insights.
This quarter we've got an exciting new enhancement 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:
| Table of Contents |
|---|
1. Introducing 20 new datasets for our new Control Module
With the release of our revamped Controls Module, a set of new Control datasets will be introduced within Camms.Insights. These datasets will align with key areas of the module such as: control details, documents, and links.
New datasets created are as follows.
Control_ControlDetails_STND
Control_ControlDocuments_STND
Control_ControlActionDetails_STND
Control_ControlCausesLink_STND
Control_ControlConsequencesLink_STND
Control_ControlOrgHierarchyLink_STND
Control_ControlCustomHierarchyLink_STND
Control_ControlFlexOrgHierarchyLink_STND
Control_ControlFlexOrgHierarchyLinkRollup_STND
10. Control_DeletedControls_STND
11. Control_ControlRiskLink_STND
12. Control_ControlIncidentLink_STND
13. Control_ControlAuditLink_STND
14. Control_ControlAuditRecommendationLink_STND
15. Control_ControlAuditFindingLink_STND
16. Control_ControlComplianceLink_STND
17. Control_ControlAuthorityDocumentLink_STND
18. Control_ControlPolicyLink_STND
19. Control_ControlKPILink_STND
20. Control_ControlRegister_STND
1.1. Control_ControlDetails_STND
This dataset enables you to generate reports based on the data from the Control Details page. of the Control module.
All standard and custom fields enabled (ticked) from the Control Settings > Field Configuration > Details tab against the 'Control Detail' column, are included in this dataset dynamically.
Additionally, it includes several fixed fields such as:
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
...
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | All the common control related linked datasets. (e.g. Control_ControlIncidentLink_STND) |
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:
1.2 Control_ControlDocuments_STND
This dataset enables you to retrieve data of the uploaded files i.e. Documents or URLs via the Control module when the Documents area is activated via Control Settings.
The fields are as follows:
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
DOCUMENTID | Text | This is a unique identifier for each file document or URL, and can be used to connect with other datasets |
Type | Text | The type of the file e.g., Document, URL |
Name | Text | The name of the file (Document or URL) |
Description | Text | Description about the file (Document or URL) |
Date Uploaded | Text | The date the file (Document or URL) was uploaded |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlDocuments_STND |
1.3 Control_ControlActionDetails_STND
The data for the Control_ControlActionDetails_STND dataset will be retrieved from the Control module, when the Control Solution Grid is enabled (ticked) from the Control Settings > Field Configuration > Details tab against the 'Control Detail' column.
...
The fixed fields are as follows:
Field Name | Data Type | Remarks |
CONTROLACTIONID | Text | This is a unique identifier for each control action and can be used to connect with other datasets |
Action Title | Text | The name of the control action |
Responsible Officer | Text | The name of the responsible officer |
Business Unit | Text | The name of the business unit of control |
Start Date | Text | Starting date of the action |
End Date | Text | Ending date of the action |
Action Status | Text | Status of the action |
Percentage Complete | Text | Action completed percentage |
Progress Comment | Text | Comment on the action progress |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
Organisation Links | Text | The organisational linkage as a breadcrumb (e.g. Organisation > Finance Office > Bursar) |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlActionDetails_STND | CONTROLID |
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:
1.4 Control_ControlCausesLink_STND
This dataset will present how a control record in the Control module is linked to its causes.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
CAUSEID | Text | This is a unique identifier for each cause and can be used to connect with other datasets |
Cause Title | Text | The name of the cause |
SYSTEMPERIODID | Text | This is a unique identifier for system periods |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlCausesLink_STND | CONTROLID |
1.5 Control_ControlConsequencesLink_STND
This dataset will present how a control record in the Control module is linked to its consequences.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
SYSTEMPERIODID | Text | This is a unique identifier for system periods |
CONSEQUENCEID | Text | This is a unique identifier for each consequence and can be used to connect with other datasets |
Consequence Title | Text | The name of the consequence |
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 | Control_ControlConsequences_STND | CONTROLID | = | Control_ControlConsequencesLink_STND | CONTROLID |
1.6 Control_ControlOrgHierarchyLink_STND
This dataset will present how a control record in the Control module is linked to your organisation hierarchy.
Field Name | Data Type | Remarks |
HIERARCHYNODEID | Text | This is a unique identifier for each node and can be used to connect with other datasets |
Hierarchy Node | Text | The name of the hierarchy node |
Hierarchy Name | Text | The name of the hierarchy |
HIERARCHYLEVELID | Text | This is a unique identifier for each hierarchy level and can be used to connect with other datasets |
Hierarchy Level | Text | The level of the hierarchy |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlOrgHierarchyLink_STND | CONTROLID |
1.7 Control_ControlCustomHierarchyLink_STND
This dataset will present how a control record in the Control module is linked to your organisation's custom hierarchy.
Field Name | Data Type | Remarks |
HIERARCHYNODEID | Text | This is a unique identifier for each node and can be used to connect with other datasets |
Hierarchy Node | Text | The name of the hierarchy node |
Hierarchy Name | Text | The name of the hierarchy |
HIERARCHYLEVELID | Text | This is a unique identifier for each hierarchy level and can be used to connect with other datasets |
Hierarchy Level | Text | The level of the hierarchy |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
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 |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlCustomHierarchyLink_STND | CONTROLID |
1.8 Control_ControlFlexOrgHierarchyLink_STND
This dataset will present how a control record in the Control module is linked to your organisation's flexible hierarchy.
| Info |
|---|
Note: This feature is currently applicable only to customers who have enabled the new Flexible Hierarchy permission structure, which is currently in beta. |
Field Name | Data Type | Remarks |
HIERARCHYNODEID | Text | This is a unique identifier for each hierarchy node and can be used to connect with other datasets |
HIERARCHYLEVELID | Text | This is a unique identifier for each hierarchy level and can be used to connect with other datasets |
HIERARCHYID | Text | This is a unique identifier for each hierarchy and can be used to connect with other datasets |
Hierarchy Name | Text | The name of the hierarchy |
Hierarchy Node | Text | The name of the hierarchy node |
Hierarchy Level | Text | The level of the hierarchy |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlFlexOrgHierarchyLink_STND | CONTROLID |
1.9 Control_ControlFlexOrgHierarchyLinkRollup_STND
This dataset will present how a control record in the Control module is directly linked to a particular node or to any nodes below it (rolled-up) in your flexible hierarchy.
| Info |
|---|
Note: This feature is currently applicable only to customers who have enabled the new Flexible Hierarchy permission structure, which is currently in beta. |
Field Name | Data Type | Remarks |
HIERARCHYNODEID | Text | This is a unique identifier for each hierarchy and can be used to connect with other datasets |
HIERARCHYLEVELID | Text | This is a unique identifier for each hierarchy level and can be used to connect with other datasets |
HIERARCHYID | Text | This is a unique identifier for each hierarchy and can be used to connect with other datasets |
Hierarchy Name | Text | The name of the hierarchy |
Hierarchy Node | Text | The name of the hierarchy node a control record is directly linked or rolled up to |
Hierarchy Level | Text | The name of the hierarchy level a control record is directly linked or rolled up to |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlFlexOrgHierarchyLinkRollup_STND | CONTROLID |
1.10 Control_DeletedControls_STND
This dataset retrieves any controls that have been deleted through the Control module.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
Deleted Control Title | Text | The name of the deleted control |
Deleted By (Username) | Text | The name of the user who deleted the control |
Deleted By (Linked Staff) | Text | Linked staff name of who deleted the control |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_DeletedControls_STND | CONTROLID |
1.11 Control_ControlRiskLink_STND
This dataset will present how a control record in the Control module is linked to Risks.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
RISKID | Text | This is a unique identifier for each risk and can be used to connect with other datasets |
Risk Title | Text | The name of the risk |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlRiskLink_STND | CONTROLID |
1.12 Control_ControlIncidentLink_STND
This dataset will present how a control record in the Control module is linked to Incidents.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
INCIDENTID | Text | This is a unique identifier for each incident and can be used to connect with other datasets |
Incident Title | Text | The name of the incident |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlIncidentLink_STND | CONTROLID |
1.13 Control_ControlAuditLink_STND
This dataset will present how a control record in the Control module is linked to Audits.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
AUDITID | Text | This is a unique identifier for each audit and can be used to connect with other datasets |
Audit Title | Text | The name of the audit |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlAuditLink_STND | CONTROLID |
1.14 Control_ControlAuditRecommendationLink_STND
This dataset will present how a control record in the Control module is linked to Audit Recommendations.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
RECOMMENDATIONID | Text | This is a unique identifier for each recommendation and can be used to connect with other datasets |
Recommendation Title | Text | The name of the audit recommendation |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlAuditRecommendationLink_STND | CONTROLID |
1.15 Control_ControlAuditFindingLink_STND
This dataset will present how a control record in the Control module is linked to Audit Findings.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
Finding Title | Text | The name of the audit finding |
AUDITFINDINGID | Text | This is a unique identifier for each audit finding and can be used to connect with other datasets |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlAuditFindingLink_STND | CONTROLID |
1.16 Control_ControlComplianceLink_STND
This dataset will present how a control record in the Control module is linked to Compliance records.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
COMPLIANCEID | Text | This is a unique identifier for each compliance record and can be used to connect with other datasets |
Compliance Title | Text | The name of the compliance record |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlComplianceLink_STND | CONTROLID |
1.17 Control_ControlAuthorityDocumentLink_STND
This dataset will present how a control record in the Control module is linked to Authority Documents.
Field Name | Data Type | Remarks |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
AUTHORITYDOCUMENTID | Text | This is a unique identifier for each authority document and can be used to connect with other datasets |
Authority Document Title | Text | The name of the authority document |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlAuthorityDocumentLink_STND | CONTROLID |
1.18 Control_ControlPolicyLink_STND
This dataset will present how a control record in the Control module is linked to Policies.
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 |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlPolicyLink_STND | CONTROLID |
1.19 Control_ControlKPILink_STND
This dataset will present how a control record in the Control module is linked to KPIs.
Field Name | Data Type | Remarks |
KPIID | Text | This is a unique identifier for each KPI and can be used to connect with other datasets |
KPI Title | Text | The name of the KPI |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Title | Text | The name of the control |
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 | |
LEFT | Control_ControlDetails_STND | CONTROLID | = | Control_ControlKPILink_STND | CONTROLID |
1.20 Control_ControlRegister_STND
This dataset enables you to generate reports based on the data from the Control Register page of the Control module.
All standard and custom fields enabled (ticked) from the Control Settings > Register Configuration > Register Type: Control Register against the 'Visible' column, are included in this dataset dynamically.
Additionally, it includes several fixed fields such as:
Field Name | Data Type | Remarks |
CONTROLREGISTERID | Text | This is a unique identifier for each control register and can be used to connect with other datasets |
CONTROLID | Text | This is a unique identifier for each control and can be used to connect with other datasets |
Control Name | Text | The name of the control |
Control Type | Text | The name of the control type |
The dynamic fields will appear depending on what you tick in the Visible column.
...
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 | |
LEFT | Control_ControlRegister_STND | CONTROLID | = | All the common control related linked datasets (e.g. Control_ControlIncidentLink_STND) | CONTROLID |
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:
2. Introducing new datasets to retrieve data from Child Risks in Risk Aggregation
Four (4) separate Risk datasets for each risk type is introduced in order to present the parent-child relationship of the risks (i.e.to show the parent risk along with the related child risks). These four datasets will capture all the child risks under each of the respective risk types.
Risk_StrategicChildRiskLinks_STND
Risk_OperationalChildRiskLinks_STND
Risk_ProjectChildRiskLinks_STND
Risk_CorporateChildRiskLinks_STND
The following fields are available in the dataset:
Field Name | Datatype | Remarks |
CHILDRISKID | Text | This is a unique identifier for each child risk and can be used to link with other datasets. |
RISKID | Text | This is a unique identifier for each child risk and can be used to link with other datasets. |
Risk Title | Text | Title of the risk (parent risk) |
Assessment Type | Text | The risk assessment type (i.e. Initial, Revised, Future) |
Child Risk Title | Text | Title of the child risk |
Child Risk Rating Score | Numeric | Risk rating score of the child risk (e.g. 18, 21) |
Child Risk Rating Description | Text | Risk rating description of the child risk (e.g. High, Low) |
This dataset can be joined with other standard datasets using the RISKID to obtain other standard information on risks such as Primary Risk Rating, Risk Responsible Officer.
Join Type | Data Object | Join Field | Foreign Data Object | Join Field | |
INNER | Risk_StrategicRiskInitial_STND | RISKID | = | Risk_StrategicChildRiskLinks_STND | RISKID |
Similar to the above relationship, the rest of the Child Risk Link datasets can be joined along with the corresponding Risk Assessment dataset for usage (e.g. Risk_OperationalRiskRevised_STND, Risk_ProjectRiskFuture_STND).
...