cammsinsights | December Feature Release Note

1. Introducing two new Risk datasets to incorporate the Bow-tie functionality of Controls, Causes and Consequences in cammsrisk

Introducing two new Risk datasets namely Risk_RiskControlConsequencesLink_STND and Risk_RiskControlCausesLink_STND to incorporate the functionality of linking controls to specific causes and consequences.

Figure 1.1: Risk Control Consequences Grid
Figure 1.2: Risk Control Consequences Grid

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

Following 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

Join Type

Data Object

Join Field


 

Foreign Data Object

Join Field

LEFT

 Risk_RiskControlDetails_STND

 CONTROLID

=

 Risk_RiskControlConsequencesLink_STND

 CONTROLID

LEFT

 Risk_RiskControlDetails_STND

 CONTROLID

=

 Risk_RiskControlCausesLink_STND

 CONTROLID

Table 1: Default Relationships

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

Data Model/Relationships

2. Introducing the Compliance Details dataset

Introducing the Compliance_ComplianceDetails_STND dataset, which will enable you to create reports, using the fields from the standard Compliance Details object. 

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

3. Ability to create dedicated datasets for every Compliance register

This new feature will allow you to generate a dedicated dataset for each Compliance register you configure in the Compliance solution.

  • A button is available on the register configuration screen as shown. When clicked, it will create a dataset for the respective register. The name of the dataset will be taken from the ‘Description’ field as follows;

e.g. Compliance_[Description]Register_REG

  • The suffix will be REG to denote that this is a register type dataset.

  • This dataset will include all fields configured for the respective register.

  • Any multi value field will show as comma separated values in the dataset.

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

4. Ability to create datasets for Compliance Custom Tables and Custom Objects

This feature will allow you to generate datasets for each of the Custom Tables and Custom Objects you configure in the Compliance solution.

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