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 3rd September 2022 and will be available in your Live instance on 17th September 2022
--------------------------------------------------------------------------------------------------------------------------------
1. Introducing new datasets for Actions and Review Objects in the Compliance module of Camms.Risk
These new datasets will be introduced to capture Actions and Review data in the Authority Document and Policy components of the Compliance module.
1.1 Compliance_AuthorityDocumentActions_STND
This dataset will show all fields activated for the Standard Compliance Authority Document Actions object. All fields enabled under the 'Visible' column, under Menu > Compliance Settings > Object Configuration > Authority Document Register > Action Object are included in the dataset.
Figure 1.1: Authority Document Action Object settings
This table includes static fields and all fields made visible with the above field configuration.
Field Name | Data Type | Remarks |
AUTHORITYDOCUMENTID | Text | Unique identifier for Compliance Authority Documents – not usually displayed in reports. |
Authority Document Title | Text | Name of the Authority Document. |
AUTHORITYDOCUMENTACTIONID | Text | Unique identifier for Authority Document Actions – not usually displayed in reports. |
This table includes the default relationship you can set up as a System Administrator.
Join Type | Data Object | Join Field | | Foreign Data Object | Join Field |
LEFT | <Core Authority Document Register of the user> e.g. Compliance_ComplianceAuthorityDocument_REG | AUTHORITYDOCUMENTID | = | Compliance_AuthorityDocumentActions_STND | AUTHORITYDOCUMENTID
|
1.2 Compliance_AuthorityDocumentReview_STND
This dataset will show all fields activated for the Standard Compliance Authority Document Review object. All fields enabled via Menu > Compliance Settings > Object Configuration > Authority Document Register > Review Object, will be included in the dataset.
Figure 1.2: Authority Document Review Object settings
This table includes static fields and all fields made visible with the above field configuration.
Field Name
| Data Type
| Remarks
|
AUTHORITYDOCUMENTID | Text | Unique identifier for Compliance Authority Documents – not usually displayed in reports. |
Authority Document Title | Text | Name of the Authority Document. |
AUTHORITYDOCUMENTREVIEWID | Text | Unique identifier for Authority Document reviews – not usually displayed in reports. |
This table includes the default relationship you can set up as a System Administrator.
Join Type | Data Object | Join Field | | Foreign Data Object | Join Field |
LEFT | <Core Authority Document Register of the user> e.g., Compliance_ComplianceAuthorityDocument_REG | AUTHORITYDOCUMENTID
| = | Compliance_AuthorityDocumentReview_STND
| AUTHORITYDOCUMENTID
|
1.3 Compliance_PolicyActions_STND
This dataset will show all fields activated for the Standard Compliance Policy Actions object. All fields enabled via Menu > Compliance Settings > Object Configuration > Policy Register > Action Object, are included in the dataset.
Figure 1.3: Policy Register
This table includes static fields and all fields made visible from the above field configuration.
Field Name | Data Type | Remarks |
POLICYDOCUMENTID | Text | Unique identifier for Policy Documents – not usually displayed in reports. |
Policy Document Title | Text | Name of the Policy Document. |
POLICYID | Text | Unique identifier for policies – not usually displayed in reports. |
This table includes the default relationship you can set up as a System Administrator.
Join Type | Data Object | Join Field | | Foreign Data Object | Join Field |
LEFT | <Core Policy Register of the user> e.g., Compliance_CompliancePolicy_REG | POLICYID | = | Compliance_PolicyActions_STND | POLICYID
|
2. Introducing new datasets for hierarchy linkages in Camms.Risk
New datasets will be introduced to present how a Risk record in Camms.Risk is linked to the Organisation and Planning Hierarchies of the Organisation.
2.1 Risk_RiskOrgHierarchyLink_STND
This dataset captures the linkage between Risks and the Organisational Hierarchy.
This table includes fields in the dataset.
Field Name | Data Type | Remarks |
Risk Title | Text | This captures the name of the Risk. |
RISKID | Unique ID | This unique ID can be used to link with the other datasets. |
Hierarchy Node | Text | This field captures the last node which the Risk is linked to. |
HIERARCHYNODEID | Unique ID | This unique ID can be used to link with the other datasets. |
Hierarchy Level | Text | This field captures the hierarchy level which the Risk is linked to. |
This table includes the default relationship you can set up as a System Administrator.
Join Type | Data Object | Join Field |
| Foreign Data Object | Join Field |
INNER | Planning_OrgHierarchy_STND | HIERARCHYNODEID | = | Risk_RiskOrgHierarchyLink_STND | HIERARCHYNODEID |
2.2 Risk_RiskPlanningHierarchyLink_STND
This dataset captures the linkage between Risks and the Planning Hierarchy.
This table includes fields in the dataset.
Field Name | Data Type | Remarks |
Risk Title | Text | This captures the name of the Risk. |
RISKID | Text | This unique ID can be used to link with the other datasets. |
Hierarchy Node | Text | This field captures the node which the Risk is linked to. |
HIERARCHYNODEID | Text | This unique ID can be used to link with other datasets. |
Hierarchy Level | Text | This field captures the hierarchy level which the Risk is linked to. |
This table includes the default relationship you can set up as a System Administrator.
Join Type | Data Object | Join Field |
| Foreign Data Object | Join Field |
INNER | Planning_PlanningHierarchy_STND | HIERARCHYNODEID | = | Risk_RiskPlanningHierarchyLink_STND | HIERARCHYNODEID |
3. Introducing new datasets for custom hierarchy linkages in the Camms.Risk Compliance module
These new datasets will be introduced to present how an Authority Document or a Policy under the Compliance module is linked to any Custom Hierarchy of the Organisation.
3.1 Compliance_AuthorityDocumentCustomHierarchyLink_STND
This dataset enables Authority Documents to be displayed based on their linkage with various Custom Hierarchies in the Organisation.
This table includes fields in the dataset.
Field Name | Data Type | Remarks |
Authority Document Name | Text | Name of the Authority Document. |
AUTHORITYDOCUMENTID | Text | This unique ID can be used to link with other datasets. |
Hierarchy Node | Text | This is name of the node which the Authority Document is linked to. |
HIERARCHYNODEID | Text | Unique identifier for hierarchy nodes – not usually displayed in reports. |
Hierarchy Node Level | Text | The name of the node level such as Directorate, Business Unit, etc. |
HIERARCHYNODELEVELID | Text
| Unique identifier for hierarchy node levels – not usually displayed in reports. |
Hierarchy Name | Text | Name of the hierarchy. |
HIERARCHYID | Text
| Unique identifier for hierarchies – not usually displayed in reports. |
This table includes the default relationship you can set up as a System Administrator.
Join Type | Data Object | Join Field |
| Foreign Data Object | Join Field |
INNER | <Core Authority Document Register of the user> e.g., Compliance_ComplianceAuthorityDocument_REG> | AUTHORITYDOCUMENTID | = | Compliance_AuthorityDocumentCustomHierarchyLink_STND | AUTHORITYDOCUMENTID |
3.2 Compliance_PolicyCustomHierarchyLink_STND
This dataset enables Policies to be displayed based on their linkage with various Custom Hierarchies in the Organisation.
This table includes fields in the dataset.
Field Name | Data Type | Remarks |
Policy Name | Text | Name of the Policy. |
POLICYID | Text | This unique ID can be used to link with the other datasets. |
Hierarchy Node | Text | This is name of the node which the policy is linked to. |
HIERARCHYNODEID | Text | Unique identifier for hierarchy nodes – not usually displayed in reports. |
Hierarchy Node Level | Text | The name of the node level such as Directorate, Business Unit, etc. |
HIERARCHYNODELEVELID | Text
| Unique identifier for hierarchy node levels – not usually displayed in reports. |
Hierarchy Name | Text | Name of the hierarchy. |
HIERARCHYID | Text | Unique identifier for hierarchies – not usually displayed in reports. |
This table includes the default relationship you can set up as a System Administrator.
Join Type | Data Object | Join Field |
| Foreign Data Object | Join Field |
INNER | <Core Policy Register of the user> e.g., Compliance_CompliancePolicy_REG | POLICYID | = | Compliance_PolicyCustomHierarchyLink_STND | POLICYID
|
4. Introducing a new dataset for the Vendor Register Standard Object in Camms.Project
A new dataset will be introduced to capture information related to the Standard Project object 'Vendor Register'.
- Project_VendorRegister_STND
This dataset enables you to generate reports based on the fields that are visible (ticked) in the Vendor Register object of Camms.Project. Fields can be enabled through the Project Workflows > click the Workflow > click the Vendor Register Object.
Figure 4: Vendor Register
This table includes fields in the dataset.
| Field Name | Data Type | Remarks |
| VENDORID | Text | Unique identifier for Vendors – not usually displayed in reports. |
| Vendor Name: | Text | Name of the Vendor. |
| Address | Text | Address of the Vendor. |
| Text | Email Address of the Vendor. | |
| Phone | Text | Contact Number of the Vendor. |
| Active | Text | Active status of the vendor. |
| PROJECTID | Text | Unique identifier for Projects – not usually displayed in reports. |
| Project Workflow | Text | Name of the Project Workflow. |
| Project Phase | Text | Name of the Project Phase. |
| Project Name | Text | Name of the Project. |
This table includes the default relationship for this dataset, that you can set up as an Insights Administrator.
| Join Type | Data Object | Join Field | Foreign Data Object | Join Field | |
| LEFT | Project_ProjectRegister_STND | PROJECTID | = | Project_VendorRegister_STND | PROJECTID |
5. Enhancement to the User List Standard dataset in Camms.Strategy
The Planning_UserList_STND dataset in Camms.Strategy will be modified to include 'Days Since Last Login' and 'Last Login Date/Time' as two new fields.
| Field Name | Data Type | Remarks |
| Days Since Last Login | Numeric | Number of days since last log in. |
| Last Login Date/Time | DateTime | Date and time of last log in instance. |
- To ensure these modifications are applied to the datasets for use within your Camms.Insights application, please click the link below and follow the steps:
https://cammsgroup.freshdesk.com/support/solutions/articles/43000506771-administration-updating-datasets-for-configuration-changes
6. Camms.Insights Product Upgrade – New Features and Improvements
We’re excited to inform you that Camms.Insights will be upgraded by bringing in novel features, while fixing previously identified application defects. Further information about this upgrade will be communicated via email in the coming months. Stay tuned!
