Feature Release Note | cammsinsights, June 2020
- amani imtiyas
CAMMS is pleased to announce the June Feature Release for cammsinsights.
This was released on 26th June 2020 and includes the following new features and enhancements to improve your user experience within the system.
1. Introducing a new dataset to capture the staff time entry data in cammsproject |
We are introducing a new dataset named Project_StaffTimeEntry_STND to capture the staff time entry data in cammsproject. This dataset will allow you to generate reports based on the staff's input on the tasks they are working on.
To ensure this new dataset is enabled for use within your cammsinsights application. Please follow the steps in the link below:
Below you'll find 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 |
|---|---|---|---|---|---|
LEFT | Project_ProjectRegister_STND | PROJECTID | = | Project_StaffTimeEntry_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)
2. Introducing a new dataset for Compliance and Authority Document linkage |
A new dataset by the name Compliance_ComplianceAuthorityDocumentLink_STND will be introduced to capture the linkages between Compliances and Authority Documents in cammscompliance.
Following are the fields included in the dataset:
Field Name | Data Type | Notes |
|---|---|---|
Compliance Title | Text | This field will retrieve the Title of the Compliance into your report |
COMPLIANCEID | Unique ID | This is a unique ID for each Compliance and you can use this to link with other datasets |
Authority Document Title | Text | This field will retrieve the title of the Authority Document into your reports |
AUTHORITYDOCUMENTID | Unique ID | This is a unique ID for each Authority Document and you can use this to link with other datasets |
To ensure this new dataset is enabled for use within your cammsinsights application. Please follow the steps in the link below:
Below you'll find 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 | Compliance_ComplianceDetails_STND | COMPLIANCEID | = | Compliance_ComplianceAuthorityDocumentLink_STND | COMPLIANCEID |
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 to get the Incident History data |
You now have a new dataset by the name Incident_IncidentHistory_STND will be introduced to capture the history data for each Incident in cammsincident.
You can utilize this dataset to retrieve history data within your cammsinsights reports by linking with any of the cammsincident register datasets you use. Filtered by the Incident title or the username (person who made the modification) would help you to generate more precise reports too.
Following are the fields included in the dataset:
Field Name | Data Type | Notes |
|---|---|---|
INCIDENTID | Unique ID | This is a unique ID for each Incident and you can use this to link with other datasets |
Incident Title | Text | This field will retrieve the Title of the Incident into your report |
User Name | Text | User Name of the person logged in at the time |
Time Stamp | DateTime | Date and time of the log |
Summary | Text | Summary of the modification |
Follow the steps in the link below to ensure this new dataset is enabled for use within your cammsinsights application
Below you'll find 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 |
|---|---|---|---|---|---|
LEFT | Incident_IncidentDetails_STND | INCIDENTID | = | Incident_IncidentHistory_STND | INCIDENTID |
For instructions on using the Relationships tab in your Insights Administration area, please refer:
Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)
4. Introducing two new datasets to capture Incident email notification logs |
Two new datasets will be introduced for the incident email notification log, allowing users to extract reports on all notifications sent out by the system, including details around recipients, subject and timestamp.
Following are the two new datasets that will be introduced:
Incident_EmailNotificationLog_STND
Incident_EmailNotificationBody_STND
Following are the fields included in the Incident_EmailNotificationLog_STND dataset:
FieldName | Data Type | Notes |
|---|---|---|
NOTIFICATIONID | Unique ID |
|
INCIDENTID | Unique ID | This field enables to identify an Incident uniquely. |
Incident Title | Text | This field records the title of the Incident |
Time Stamp | Date Time | This field records the Date and Time of the email execution. |
Subject | Text | This field records the subject of the email sent. |
Recipient | Text |
E.g. Five recipients = Five rows in the dataset. |
Email Type | Text | This field will record the type of email sent to the recipients.  |
Notification | Text | This field will record the name of the email notification sent to the recipients.  |
Trigger Criteria | Text | This field will record the event which triggered the email notification.  |
Following are the fields included in the Incident_EmailNotificationBody_STND dataset:
Note: Please note that this dataset is meant to be used for forensic purposes, hence the 'Email Body' field extracts the content of the email with the HTML tags.
If you need to utilize this dataset to get the email body's content only, you can use an HTML editor.
Field Name | Data Type | Notes |
|---|---|---|
NOTIFICATIONID | Email Body |
|
Email Body | Text | This field will contain the contents of the email body for each notification. |
Follow the steps in the link below to ensure this new dataset is enabled for use within your cammsinsights application.
Below you'll find 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 |
|---|---|---|---|---|---|
LEFT | Incident_IncidentDetails_STND | INCIDENTID | = | Incident_EmailNotificationLog_STND | INCIDENTID |
LEFT | Incident_IncidentDetails_STND | INCIDENTID | = | Incident_EmailNotificationLog_STND | INCIDENTID |
For instructions on using the Relationships tab in your Insights Administration area, please refer:
Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)
5. Modifications to the Risk Control Details dataset to comply with Controls that are unique for Risk feature |
The Risk_RiskControlDetails_STND dataset will be modified to capture the features that are unique for risk, in each risk control. With this modification, you will be able to generate Insights reports based on the fields that are configured as 'Unique for Risk' in cammsrisk.
6. Modifications to the Project register dataset to retrieve the current comment details for a project |
The Project_ProjectRegister_STND dataset will be modified to capture the current comment details for each project. This modification will enable you to include two new fields to your Insights reports.
Following are the fields that will be included to the Project_ProjectRegister_STND dataset:
Project Current Comment Updated By
Project Current Comment Updated Date
Â