Feature Release Note | cammsinsight, January 2020

1. Overview 

 CAMMS is pleased to announce the January Feature Release for cammsinsights

This includes a number of new features and enhancements to improve your user experience within the system. The release is set for the 24th of January 2020, and will include the following features.

2. Introducing a new dataset for Risk Secondary Owners in cammsrisk

The new Risk_RiskOwnerLink_STND dataset will enable users to generate reports based on cammsrisk Secondary Owners data.

Fields included in the dataset:

Field Name

Notes

Field Name

Notes

Primary Risk Owner

Name of the primary risk owner

PRIMARYRISKOWNERID

Unique ID of the primary risk owner

Risk Title

Name of the Risk

RISKID

Unique ID of the Risk

Secondary Risk Owner

Name of the secondary risk owner

SECONDARYRISKOWNERID

Unique ID of the secondary risk owner

To ensure this new dataset is enabled for use within your cammsinsights application, please follow the steps in the link below: 

Administration: Configuring and enabling new datasets for use - Camms.Support Documentation - Confluence (atlassian.net)

Below are the default relationships for this new dataset - you can set these up as an Insights Administrator.

Join Type

Data Object

Join Field


 

Foreign Data Object

Join Field

INNER

Risk_StrategicRiskInitial_STND

RISKID

=

Risk_RiskOwnerLink_STND

RISKID

INNER

Risk_OperationalRiskInitial_STND

RISKID

=

Risk_RiskOwnerLink_STND

RISKID

INNER

Risk_CorporateRiskInitial_STND

RISKID

=

Risk_RiskOwnerLink_STND

RISKID

INNER

Risk_ProjectRiskInitial_STND

RISKID

=

Risk_RiskOwnerLink_STND

RISKID

For instructions on using the Relationships tab in your Insights Administration area, please refer:

Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)

3. Introducing a new dataset for Secondary Service Profiles in cammsproject

The new Project_ProjectServiceLink_STND dataset will include both the project's primary and secondary service profiles with corresponding ID fields enabling Insights report writers to join these with other datasets and display these Service Profiles in reports.

Fields included in the dataset:

Field Name

Notes

Field Name

Notes

PROJECTID

Unique ID for the Project

Project Name

Name of the Project

PRIMARYSERVICEID

Unique ID for the Primary Service

Primary Service

Name of the Primary service

SECONDARYSERVICEID

Unique ID for the Secondary service

Secondary Service

Name of the Secondary service

To ensure this new dataset is enabled for use within your cammsinsights application, please follow the steps in the link below: 

Administration: Configuring and enabling new datasets for use - Camms.Support Documentation - Confluence (atlassian.net)

Below are the default relationships for these new datasets which you can set up as an Insights Administrator.

Join Type

Data Object

Join Field

 

Foreign Data Object

Join Field

INNER

Project_ProjectRegister_STND

PROJECTID

=

Project_ProjectServiceLink_STND

PROJECTID

For instructions on using the Relationships tab in your Insights Administration area, please refer:

Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)

4. Ability to fetch data from the current/latest phase of Project Custom Tables

The current facility which allows you to create your own dataset for custom tables will be further extended by allowing you to create two possible datasets for each custom table. As such you can have;

  1. A dataset which produces data from all phases of the project which includes a custom table of the same name (which is currently available).

  2. A dataset which will always retrieves data from the current or latest phase where the particular custom table sits in (this will be a new option from this release).

 In order for you to generate the Insights datasets, a drop down called ‘Create Insights Dataset’ is now available in the custom table configuration pop-up in cammsproject as shown below;

Figure 4.1: Dropdown to create Insights Dataset in cammsproject

There are two options provided for you in the drop down as below;

  1. Create for all phases

Selecting this option will provide the current functionality of the “Create Insights Dataset” button which produces a dataset which draws data from all workflows and phases where a custom table of the same name exists.

E.g. If the custom table name is “MyTable”, then the dataset will be “Project_MyTable_TBL”

2. Create for Current phases

Selecting this option will create a dynamic dataset which always pulls data for the custom table from the current phase of the project. Therefore, when this option is selected, a new dataset will be created for the custom table and the dataset name will be taken from the custom table name appended with ‘CurrentPhase’.

E.g. If the custom table name is “MyTable”, then the dataset will be “Project_MyTableCurrentPhase_TBL”

Note:

  • If the same custom table is used multiple times in the same phase, then the first custom table is considered to create the dataset. And if the current phase does not contain the custom table, then the latest custom table from the previous phase will be considered.

  • This modification requires that the custom tables should be configured with the same columns and rows across multiple workflows and phases to avoid report crashes upon moving a project from one phase to another.

Apart from the column names you configure in cammsproject for the relevant custom table, the following standard fields will also be available in the custom dataset;

Field name

Data type

Notes

Field name

Data type

Notes

PROJECTID

Unique Identifier

To identify the project uniquely

Project Name

Text

Name of the Project

Workflow Name

Text

Name of the workflow

Current Project Phase

Text

Name of the current phase

Row Title

Text

This field will contain the row names

Custom Object Name

Text

Name of the custom object

Custom Table Name

Text

Name of the custom table

5. Introducing new datasets to retrieve links from the Compliance module

With this release, several new datasets are made available for you to retrieve the links between different areas of the Compliance module as below.

  1. Compliance_PolicyAuthorityDocumentLink_STND

Fields included in the dataset:

Field Name

Notes

Field Name

Notes

Name

Name of the Authority document

AUTHORITYDOCUMENTID

Unique ID of the Authority document

Policy Name

Name of the Policy

POLICYID

Unique ID of the Policy

2. Compliance_CompliancePolicyLink_STND

Fields included in the dataset:

Field Name

Notes

Field Name

Notes

Compliance Title

Name of the Compliance

COMPLIANCEID

Unique ID of the Compliance

Policy Name

Name of the Policy

POLICYID

Unique ID of the Policy

3. Compliance_AuthorityDocumentLink_STND

Fields included in the dataset:

Field Name

Notes

Field Name

Notes

Name

Name of the Authority document

AUTHORITYDOCUMENTID

Unique ID of the Authority document

Linked Name

Name of the linked Authority document

LINKEDAUTHORITYDOCUMENTID

Unique ID of the linked Authority document

4. Compliance_PolicyLink_STND

Fields included in the dataset:

Field Name

Notes

Field Name

Notes

Policy Name

Name of the Policy

POLICYID

Unique ID of the Policy

Linked Policy Name

Name of the linked Policy

LINKEDPOLICYID

Unique ID of the linked Policy

5. Compliance_ComplianceRiskLink_STND

Fields included in the dataset:

Field Name

Notes

Field Name

Notes

Compliance Title

Name of the Compliance

COMPLIANCEID

Unique ID of the Compliance

Risk Title

Name of the Risk

RISKID

Unique ID of the Risk

LINKAGEID

Unique ID of the linkage

6. Compliance_ComplianceIncidentLink_STND

Fields included in the dataset:

Field Name

Notes

Field Name

Notes

Compliance Title

Name of the Compliance

COMPLIANCEID

Unique ID of the Compliance

Incident Title

Name of the Incident

INCIDENTID

Unique ID of the Incident

LINKAGEID

Unique ID of the linkage

To ensure these new datasets are enabled for use within your cammsinsights application, please follow the steps in the link below: 

Administration: Configuring and enabling new datasets for use - Camms.Support Documentation - Confluence (atlassian.net)

6. Modifications to the Action Details dataset to extract the image and the confidential fields

Two new fields namely ‘Image’ and ‘Confidential’ have been added to the Planning_ActionDetails_STND dataset. Using these fields now you can get the Image and the data from the confidential tick box of the Action to your Insights reports.

IMPORTANT: Any reports you have created using this dataset may display configuration errors after this release due to these new fields. Please update the dataset as soon as possible to ensure smooth functioning of your reports.

To update and apply the modifications to the above-mentioned dataset, please follow the steps in the link below:

Administration: Updating datasets for configuration changes - Camms.Support Documentation - Confluence (atlassian.net)