Quarterly Product Update | Camms.Insights | Apr-Jun 2021
- amani imtiyas
Camms is pleased to bring you the Quarterly Product Release Notification 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 19th June 2021 and will be available in your Live instance on 3rd July 2021.
1. New dataset for Camms.Strategy to view staff linked to the Flex Org Hierarchy |
The Planning_StaffFlexOrgHierarchyLink_STND dataset is introduced to let you view a list of staff members linked at different levels of your Flexible Organisation Hierarchy. This can be joined with the existing Staff Details dataset to present further details about each staff member if required.
Note: This feature is currently applicable only to customers who have enabled the new Flexible Hierarchy permission structure, which is currently in beta.
The following fields are included in the dataset:
Field Name | Data Type | Remarks |
STAFFID | Text | Unique ID of the Staff member that can be used to link with other related datasets |
Staff Name | Text | Captures the name of the staff member |
HIERARCHYID | Text | Unique ID of the Hierarchy that can be used to link with other related datasets |
HIERARCHYLEVELID | Text | Unique ID of the Hierarchy Level that can be used to link with other related datasets |
HIERARCHYNODEID | Text | Unique ID of the Hierarchy Node that can be used to link with other related datasets |
Hierarchy Name | Text | Captures the name of the hierarchy, that the staff member is linked to (e.g. Organisation Hierarchy) |
Hierarchy Level | Text | Captures the level of the hierarchy, the staff member is linked to (e.g. Business Unit) |
Node Name | Text | Captures the hierarchy node the staff member is linked to (e.g. Corporate Services) |
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 | Planning_StaffFlexOrgHierarchyLink_STND | STAFFID | = | Planning_Staff_STND | STAFFID |
To ensure this new dataset is enabled for use within your Camms.Insights application, please click the link below and follow the steps:
2. New standard datasets for Camms.Risk Survey |
Two new datasets will be introduced to support reporting on data from the new Camms.Risk Survey Solution. These will cover Survey Registers and Survey responses.
2.1 Survey_SurveyRegister_STND
The following fields are included in the dataset:
Field Name | Data Type | Remarks |
|---|---|---|
SURVEYID | Text | Unique ID of the survey that can be used to link with other related datasets |
Survey Title | Text | Captures the title of the survey |
Survey Description | Text | Captures a description about the survey |
Date Created | Date Time | Captures the date the survey has been created |
Due Date | Date Time | Captures the due date of the survey |
Invites Sent | Numeric | Captures the number of invitations sent to respond the survey |
Linked Obligations | Text | Captures obligations linked to the survey |
Linked Risk Controls | Text | Captures the risk controls linked to the survey |
Next Scheduled Recurrence | Date Time | Captures the next scheduled date and time of the survey |
Number of Questions | Numeric | Captures the number of questions in the survey |
Progress | Numeric | Captures the progress of the survey completion, numerically (e.g. 50%) |
Progress Status | Text | Captures the progress of the survey completion (e.g. Completed/In Progress/Not started) |
Response Rate | Numeric | Captures the response rate of the survey |
Responses Received | Numeric | Captures the number of responses received |
Response Period | Date Time | Captures the end date and time of the schedule |
Status | Text | Captures the status of the survey (e.g. Active/Closed/Draft) |
Yet To Response | Numeric | Captures the number of responses due |
2.2 Survey_SurveyResponses_STND
The following fields are included in the dataset:
Field Name | Data Type | Remarks |
|---|---|---|
SURVEYID | Text | Unique ID of the survey that can be used to link with other related datasets |
Survey Title | Text | Captures the title of the survey |
Linked Obligations | Text | Captures obligations linked to the survey |
Linked Risk Controls | Text | Captures the risk controls linked to the survey |
QUESTIONID | Text | Unique ID that can be used to link with other datasets |
Question Title | Text | Captures the title of the question |
Responded Business Unit | Text | Captures the business unit of the respondents |
Responded By | Text | Captures the name of the user that has responded |
Response | Text | Captures the response |
Response Comment | Text | Captures any comments on the response |
Response Date & Time | Date Time | Captures the date and time of the response that has been provided |
Response Period | Date Time | Captures the end date and time of the schedule |
Tags | Text | Captures the tags relevant to Survey questions. |
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 | Survey_SurveyRegister_STND | SURVEYID | = | Survey_SurveyResponses_STND | SURVEYID |
To ensure this new dataset is enabled for use within your Camms.Insights application, please click the link below and follow the steps:
3. New dataset for Camms.Strategy to obtain the Business Unit Logo for reporting |
Your existing Organisation Hierarchy dataset can now be joined with this new dataset Planning_BusinessUnitLogo_STND to obtain the uploaded logo image for each Business Unit, which can then be displayed within reports.
The following fields are included in the dataset:
Field Name | Data Type | Remarks |
|---|---|---|
BUSINESSUNITID | Text | Unique ID of the Business Unit that can be used to link with other related datasets |
Business Unit Name | Text | Captures the name of the Business Unit |
Business Unit Logo | Image | Captures the image of the corresponding Business Unit |
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 | Planning_OrgHierarchy_STND | BUSINESSUNITID | = | Planning_BusinessUnitLogo_STND | BUSINESSUNITID |
To ensure this new dataset is enabled for use within your Camms.Insights application, please click the link below and follow the steps:
4. Create your own datasets for Camms.Risk Compliance Custom Objects related to Policies |
You can now create your own datasets for each custom object configured for Policies in the Camms.Risk Compliance solution. This will enable you to report on the data held within each of these objects in your Policy related workflows.
To ensure this new dataset is enabled for use within your Camms.Insights application, please click the link below and follow the steps:
5. New datasets for Camms.Risk Incident to view incidents linked to the Flex Org Hierarchy |
Two new datasets will be introduced that will let you view Incidents linked to the different levels of the Flexible Organisation Hierarchy. Incident_IncidentFlexOrgHierarchyLink_STND will allow you to obtain the Incidents that are linked directly to a particular node such as Corporate Services. Incident_IncidentFlexOrgHierarchyLinkRollup_STND on the other hand will allow you to view Incidents that are linked either directly to a particular node or to any nodes below it (rolled-up).
Note: This feature is currently applicable only to customers who have enabled the new Flexible Hierarchy permission structure, which is currently in beta.
5.1 Incident_IncidentFlexOrgHierarchyLink_STND
The following fields are included in the dataset:
Field Name | Data Type | Remarks |
|---|---|---|
INCIDENTID | Text | Unique ID for the Incident that can be used to link with other related datasets |
Incident Title | Text | Captures the title of the incident |
HIERARCHYID | Text | Unique ID of the Hierarchy that can be used to link with other related datasets |
HIERARCHYLEVELID | Text | Unique ID of the Hierarchy Level that can be used to link with other related datasets |
HIERARCHYNODEID | Text | Unique ID of the Hierarchy Node that can be used to link with other related datasets |
Hierarchy Name | Text | Captures the name of the hierarchy which the incident is linked to (e.g. Organisation Hierarchy) |
Hierarchy Level | Text | Captures the level of the hierarchy which the incident is linked to (e.g. Business Unit) |
Node Name | Text | Captures the name of the hierarchy node which the incident is linked to (e.g. Corporate Services) |
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 | Incident_IncidentDetails_STND (If different workflow, use the relevant Details object dataset) | INCIDENTID | = | Incident_IncidentFlexOrgHierarchyLink_STND | INCIDENTID |
5.2 Incident_IncidentFlexOrgHierarchyLinkRollup_STND
The following fields are included in the dataset:
Field Name | Data Type | Remarks |
INCIDENTID | Text | Unique ID of the Incident that can be used to link with other related datasets |
Incident Title | Text | Captures the title of the incident |
HIERARCHYID | Text | Unique ID of the Hierarchy that can be used to link with other related datasets |
HIERARCHYLEVELID | Text | Unique ID of the Hierarchy Level that can be used to link with other related datasets |
HIERARCHYNODEID | Text | Unique ID of the Hierarchy Node that can be used to link with other related datasets |
Hierarchy Name | Text | Captures the name of the hierarchy which the incident is linked to (e.g. Organisation Hierarchy) |
Hierarchy Level | Text | Captures the level of the hierarchy which the incident is linked or rolled up to (e.g. Business Unit) |
Node Name | Text | Captures the name of the hierarchy node which the incident is linked or rolled up to (e.g. Corporate Services) |
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 | Incident_IncidentDetails_STND (If different workflow, use the relevant Details object dataset) | INCIDENTID | = | Incident_IncidentFlexOrgHierarchyLinkRollup_STND | INCIDENTID |
To ensure these new datasets are enabled for use within your Camms.Insights application, please click the link below and follow the steps:
We are pleased to inform you that the Camms.Insights application has been upgraded and now includes the below functionalities.
6. Inactive users are indicated in schedules |
Previously, users that were deactivated from the system were not indicated as ‘Inactive’, if they were used as recipients when creating a schedule. With the new upgrade, if you add an inactive user, the system indicates this as ‘Inactive’ and the user will no longer receive emails.
7. Conditional formatting can be applied against null/blank values |
Previously, conditional formatting could be applied only to a single value or all values. Now, it is available for null and blank values as well.
8. The day that begins the week can now be configured through advanced settings |
You now have the freedom to specify the starting day of the week according to your calendar, through the Insights Advanced Settings page. This will impact only if you use an ‘In time Period’ filter in the report and make the selection as 'Last week'.
9. A new checkbox has been introduced to ‘Remove Extra Side Total Columns’ in pivot grids |
Upon ticking on the ‘Add Side Total’ checkbox, the new ‘Remove Extra Side Total Columns’ checkbox gets visible. Earlier, Total Columns which used to appear in between the ‘Value’ columns, gets removed by ticking on this new checkbox, and the total columns will limit only to the right side of the grid.
10. Dashboards will only display the current slide in full screen mode |
When a dashboard is viewed full screen in presentation mode, partial views of the previous or next report parts are not visible now in the left or right margins. The margins will remain the same without showing any previous nor next report part on the screen.
Previous: Legend of the previous report partially visible | Now: |
Figure 10.1: Partial views of previous/next reports not visible in full screen mode