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 December 2022 and will be available in your Live instance on 17th December 2022.

List of items:

1 1. Introducing new standard datasets to expose obligation and control survey data in Camms.Risk Compliance
2 2. Introducing a new standard dataset to expose staff FlexOrg Hierarchy roles assigned to users in Camms.Strategy
- 2.1 2.1 Planning_StaffFlexAssignRole_STND
3 3. Introducing new datasets to capture revision history for Compliance, Policy and Authority Document modules in the Compliance application
4 4. Enhancement on default date/time columns in Project Task datasets.

1. Introducing new standard datasets to expose obligation and control survey data in Camms.Risk Compliance

New standard datasets are to be developed to link Surveys related to ‘Controls’ and ‘Obligation/Compliance’ modules in Camms.Compliance with the Survey_SurveyRegister_STND and Survey_SurveyResponses_STND datasets, that already exist in the system.

The following new link datasets have been introduced:

1.1 Survey_SurveyControlLink_ STND

This dataset will link Control Surveys with Survey_SurveyRegister_STND. The following fields will be included in this dataset to establish links with the Survey datasets.

Field Name	Data Type	Field Description
SURVEYID	int	Unique identifier for Survey in the Survey Register.
Survey Title	nvarchar	Title of Survey in the Survey Register.
CONTROLID	int	Unique identifier of the Control, linked in the Linkage tab.
Control Title	nvarchar	Title of linked Control, in the Linkage tab in the Survey Register.

1.2 Survey_SurveyResponseControlLink_STND

This dataset will link Control Survey responses with Survey_SurveyResponses_STND. The following fields will be included in this dataset to establish links with the Survey datasets.

Field Name	Data Type	Field Description
SURVEYID	int	Unique identifier for Survey in the Survey Register.
Survey Title	nvarchar	Title of Survey in the Survey Register.
CONTROLID	int	Unique identifier of the Control, linked in Linkage tab.
Control Title	nvarchar	Title of linked Control.
QUESTIONID	int	Unique identifier of Question linked in the Questions tab.
Question Title	nvarchar	Title of Question in the Questions tab.

1.3 Survey_SurveyComplianceLink_ STND

This dataset will link Compliance Surveys with Survey_SurveyRegister_STND. The following fields will be included in this dataset to establish links with the Survey datasets.

Field Name	Data Type	Field Description
SURVEYID	int	Unique identifier for Survey in the Survey Register.
Survey Title	nvarchar	Title of Survey in the Survey Register.
COMPLIANCEID	int	Unique identifier of the Compliance linked in the Linkage tab.
Compliance Title	nvarchar	Title of the linked Compliance in the Linkage tab in the Survey Register.

1.4 Survey_SurveyResponseComplianceLink_ STND

This dataset will link Compliance Survey responses with Survey_SurveyResponses_STND. The following fields will be included in this dataset to establish links with the Survey datasets.

Field Name	Data Type	Field Description
SURVEYID	int	Unique identifier for Survey in the Survey Register.
Survey Title	nvarchar	Title of Survey in the Survey Register.
COMPLIANCEID	int	Unique identifier of the Compliance linked in the Linkage tab.
Compliance Title	nvarchar	Title of linked Compliance.
QUESTIONID	int	Unique identifier of Question linked in the Questions tab.
Question Title	nvarchar	Title of the Question in the Questions tab.

The data that will be available in the dataset will be based on the components illustrated below.

The Survey ID and Title will be derived from the ‘Survey Register’ module illustrated below.

Figure 1.4.1

The Control and Compliance IDs and Titles will be derived from the ‘Linkage’ tab as illustrated below.

The Question ID and Title will be derived from the ‘Questions’ tab as illustrated below

Default relationships can be defined for these datasets as follows. A combination of SURVEYID and QUESTIONID should be used as illustrated below for the ‘Join Field’ when creating relationships for the Survey_SurveyResponses_STND dataset.

Join Type	Dataset	Join Field	=	Dataset	Join Field
LEFTOUT	Survey_SurveyRegister_ STND	SURVEYID		Survey_SurveyControlLink_ Stnd	SURVEYID
LEFTOUT	Survey_SurveyRegister_ STND	SURVEYID		Survey_SurveyComplianceLink_ Stnd	SURVEYID
LEFTOUT	Survey_SurveyResponses_ STND	SURVEYID (AND) QUESTIONID		Survey_SurveyResponseControlLink_ Stnd	SURVEYID (AND) QUESTIONID
LEFTOUT	Survey_SurveyResponses_ STND	SURVEYID (AND) QUESTIONID		Survey_SurveyResponseComplianceLink_ Stnd	SURVEYID (AND) QUESTIONID

2. Introducing a new standard dataset to expose staff FlexOrg Hierarchy roles assigned to users in Camms.Strategy

A new standard dataset will be introduced to expose the FlexOrg Hierarchy roles assigned to staff in Camms.Strategy in the 'Staff' module. The dataset will allow the FlexOrg ‘Role’ details of each staff member defined in Camms.Strategy to be generated in reports.

2.1 Planning_StaffFlexAssignRole_STND

The data that will be available in the dataset will be based on the components illustrated below within the 'Staff' module of Camms.Strategy.

Camms.Strategy Menu > Staff

Camms.Strategy Menu > Staff > Select Staff > Details

Camms.Strategy Menu > Staff > Select Staff > Assign Role >

Camms.Strategy Menu > Staff > Select Staff > Assign Role > Add New

The dataset will include the following fields.

Field Name	Data Type	Remarks
STAFFID	Unique Identifier	This is a unique identifier field for Staff details.
USERID	Unique Identifier	This is a unique identifier field for the respective User details.
HIERARCHYID	Unique Identifier	This is a unique identifier field for the respective Hierarchy details.
Hierarchy Name	Text	Hierarchy details to which a Staff member is assigned to. This should be captured from Camms.Strategy Menu > Staff > Select Staff > Assign Role > Hierarchy Name.
HIERARCHYLEVELID	Unique Identifier	This is a unique identifier field for the respective Hierarchy details.
Hierarchy Level	Text	Hierarchy details to which a Staff member is assigned to. This should be captured from Camms.Strategy Menu > Staff > Select Staff > Assign Role > Hierarchy Level.
HIERARCHYNODEID	Unique Identifier	This is a unique identifier field for the respective Hierarchy details.
Hierarchy Node	Text	Hierarchy Node details to which a Staff member is assigned to. This should be captured from Camms.Strategy Menu > Staff > Select Staff > Assign Role > Hierarchy Node.
Product	Text	This should be captured from Camms.Strategy Menu > Staff > Select Staff > Assign Role > Product.
Roles	Text	This should be captured from Camms.Strategy Menu > Staff > Select Staff > Assign Role > Roles.
Staff Member	Text	Name of the Staff Member. Camms.Strategy Menu > Staff > Select Staff > Details> Name.

This dataset can be joined with other standard datasets using the unique identifiers to obtain other related information. Given below are some examples of how the standard datasets can be joined.

Join Type	Dataset	Join Field	=	Dataset	Join Field
Left	Planning_Staff_STND	STAFF ID		Planning_StaffFlexOrgUserRoles_ STND	STAFFID
Left	Planning_UserList_STND	USER ID		Planning_StaffFlexOrgUserRoles_ STND	USERID
Left	Planning_StaffFlexOrgHierarchyLink_ STND	STAFF ID		Planning_StaffFlexOrgUserRoles_ STND	STAFFID

3. Introducing new datasets to capture revision history for Compliance, Policy and Authority Document modules in the Compliance application

New standard datasets will be introduced exposing history data from each of the components in the Camms.Risk Compliance product as follows:

Compliance_ComplianceHistoryExtended_STND
Compliance_AuthorityDocumentHistoryExtended_STND
Compliance_PolicyHistoryExtended_STND

Each of these datasets will have mandatory parameters imposed at a dataset level as follows:

New Datasets	Parameters	Remarks
Compliance_ComplianceHistory Extended_STND	@DateFrom	Start date of date range in which field revision history is required.
	@DateTo	End date of date range in which field revision history is required.
	@ComplianceObjectName	Name of object in which field revision history is required.
Compliance_ComplianceAuthorityDocument HistoryExtended_STND	@Date From	Start date of date range in which field revision history is required.
	@DateTo	End date of date range in which field revision history is required.
	@ComplianceAuthorityDocument ObjectName	Name of object in which field revision history is required.
Compliance_CompliancePolicyHistory Extended_STND	@DateFrom	Start date of date range in which field revision history is required.
	@DateTo	End date of date range in which field revision history is required.
	@CompliancePolicyObjectName	Name of object in which field revision history is required.

The following fields will be included in the datasets for creation of revision history reports.

3.1 Compliance_PolicyHistoryExtended_STND

Field Name	Data Type	Field Description
@CompliancePolicyObjectName	nvarchar	Object name selected in dataset parameter.
@DATEFROM	datetime	Start date selected in dataset parameter.
@DATETO	datetime	End date selected in dataset parameter.
Action Summary	nvarchar	Summary field in application History module.
AUDITRECORDID	Int	Unique identifier (system purposes)
Current Value	nvarchar	Current Representation in the application History module.
Field Name	nvarchar	Fields under the filtered object in the dataset parameter.
Object Name	nvarchar	Name of filtered object.
POLICYID	Int	Unique identifier for the Policy item.
Previous Value	nvarchar	Previous Representation in the application History module.
Policy Name (Standard term)	nvarchar	Name of Policy (dynamic field where field label may differ based on tenant terminology)
Time Stamp	datetime	Timestamp of revision done.
User Name	nvarchar	Name of user who has made revisions to fields.
Workflow Name	varchar	Name of workflow relevant to filtered object.
Policy Code	nvarchar	Unique identifier

3.2 Compliance_ComplianceHistoryExtended_STND

Field Name	Data Type	Remarks
@ComplianceObjectName	nvarchar	Object name selected in dataset parameter.
@DATEFROM	datetime	Start date selected in dataset parameter.
@DATETO	datetime	End date selected in dataset parameter.
Action Summary	nvarchar	Summary field in the application History module.
AUDITRECORDID	int	Unique identifier (system purposes)
COMPLIANCEID	int	Unique identifier for Obligation item.
Current Value	nvarchar	Current Representation in the application History module.
Field Name	nvarchar	Fields under the filtered Object in the dataset parameter.
Object Name	nvarchar	Name of filtered object.
Previous Value	nvarchar	Previous Representation in the application History module.
Compliance Title	nvarchar	Name of Obligation (dynamic field where field label may differ based on tenant terminology)
Time Stamp	datetime	Timestamp of revision done.
User Name	nvarchar	Name of user who has made the revision to fields.
Workflow Name	varchar	Name of workflow relevant to the filtered object.
Compliance Code	nvarchar	Unique identifier

3.3 Compliance_AuthorityDocumentHistoryExtended_STND

Field Name	Data Type	Remarks
@ComplianceAuthorityDocumentObjectName	nvarchar	Object name selected in the dataset parameter.
@DATEFROM	datetime	Start date selected in the dataset parameter.
@DATETO	datetime	End date selected in the dataset parameter.
Action Summary	nvarchar	Summary field in the application History module.
AUDITRECORDID	int	Unique identifier (system purposes)
AUTHORITYDOCUMENTID	int	Unique identifier for the Authority Document item.
Current Value	nvarchar	Current Representation in the application History module.
Authority Document Title	nvarchar	Name of Authority Document (dynamic field where field label may differ based on tenant terminology)
Field Name	nvarchar	Fields under filtered object in the dataset parameter.
Object Name	nvarchar	Name of filtered object.
Previous Value	nvarchar	Previous Representation in the application History module.
Time Stamp	datetime	Timestamp of the revision done.
User Name	nvarchar	Name of user who has made the revision to fields.
Workflow Name	varchar	Name of workflow relevant to filtered object.
Authority Document Code	nvarchar	Unique identifier

The values for dataset fields 'Action Summary', 'Current Value', and 'Previous Value' is obtained from the 'History' module in the Camms.Risk Compliance application as illustrated below.

The 'Summary' field in Camms.Risk Compliance platform 'History' module is named as 'Action Summary' in the datasets.

The 'Current Representation' field in the Compliance platform 'History' module is named as 'Current Value ' in the datasets.

The 'Previous Representation' field in the Compliance platform 'History' module is named as 'Current Value ' in the datasets.

The “Data Source” module in Camms.Insights will be modified to view the mandatory parameters of each new dataset where the 'Filter' panel will include the parameters of each dataset. The user is required to select values for these filters to select the dataset for the report 'Design'.

Illustration of parameters in the 'Data Source' selection module for Compliance_ComplianceHistoryExtended_STND dataset

Illustration of parameters in the 'Data Source' selection module for Compliance_AuthorityDocumentHistoryExtended_STND dataset.

Illustration of parameters in the 'Data Source' selection module for Compliance_PolicyHistoryExtended_STND datset.

Note: These datasets are not recommended to be joined with other datasets due to performance constraints. Each of these datasets must be used independently.

4. Enhancement on default date/time columns in Project Task datasets.

The 'Start Date' and 'End Date' fields of Project Task datasets are made static by modifying the field data type to Date/Time. The fields in the following Project Task datasets have been modified.

Project_TaskDetails_STND
Project_TaskDetailsAll_STND
Project_TaskDetailsCurrentPhase_STND

Field Name	Data Type	Remarks
Start Date	DateTime	Task start date
End Date	DateTime	Task end date

Important Note:

To ensure these modifications are applied to the datasets for use within your Camms.Insights application, please follow the guidelines given in the link below.\

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

Camms.Insights | December 2022