...
This was released on 15th August 2020 and includes the following new features and enhancements to improve your user experience within the system.
Introducing a new dataset to view KPIs by hierarchy node
The Planning_KPIsByHierarchyNode_STND dataset combines KPI data and hierarchy node data into one dataset for you to create reports using all KPIs associated with various hierarchy levels, including rollup KPIs.
Following are the fields included in the dataset:
Field name | Data Type | Notes |
|---|---|---|
DATEFROM | Date Time | Date range selection for KPI data |
DATETO | Date Time | |
KPIID | Unique identifier | Unique ID of the KPI |
KPI Name | Text | Name of the KPI |
Single/Rollup | Text | This field will retrieve whether the KPI is a single or rollup into your report |
KPI Type | Text | This field will retrieve KPI type into your report |
Calculation method | Text | This field will retrieve the Calculation Method into your report – Only applicable for calculated KPI’s |
Reporting year | Text | This field will retrieve the reporting year into your report. i.e. 19/20 |
Reporting year period | Text | This field will retrieve the reporting year period into your report. e.g. Monthly: December 2017, quarterly: Jan-Mar 2017 |
Benchmark | Numeric | This field will retrieve the Benchmark into your report. |
Forecast | Numeric | This field will retrieve the Forecast into your report |
Sort date | Date | This is a date field used to sort reporting year periods logically |
Period target | Numeric | This field will retrieve the Period Target into your report |
Period actual | Numeric | This field will retrieve the Period Actual into your report |
Period variance | Numeric | This field will retrieve the Period Variance into your report |
Period comments | Text | This field will retrieve the Period Comments into your report |
YTD target | Numeric | This field will retrieve the YTD Target into your report |
YTD actual | Numeric | This field will retrieve the YTD Actual into your report |
Hierarchy name | Text | This field will retrieve the relevant hierarchy name into your report |
Hierarchy level | Text | This field will retrieve the relevant hierarchy Level into your report e.g. Goal, Outcome |
HIERARCHYLEVELID | Unique identifier | Unique ID of the Hierarchy Level |
HIERARCHYNODEID | Unique identifier | Unique ID of the Hierarchy Node |
Node name | Text | This field will retrieve the relevant hierarchy Node name into your report |
...
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 | Planning_KPIDetails_STND | KPIID | = | Planning_KPIsByHierarchyNode_STND | KPIID |
...
Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)
Introducing a new dataset to view previous value and new value against each modified field name within an incident in Camms.Incident
The Incident_IncidentHistoryExtended_STND dataset will allow you to report previous value and new value against each modified field name within the respective incident.
Following are the fields included in the dataset:
Field name | Data Type | Notes |
|---|---|---|
Incident Title | Text | This field will retrieve the incident title of the respective field that linked to |
INCIDENTID | Unique identifier | This is a unique ID for each Incident and you can use this to link with other datasets |
User Name | Text | This field will retrieve the name of the respective field modified user |
Time Stamp | Datetime | This field will retrieve the field modified date and time |
Previous Value | Text | This field will retrieve the previous value of the respective field modified |
Field Name | Text | This field will retrieve the field name where containing value modified |
Current Value | Text | This field will retrieve the current value of the respective field modified |
...
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_IncidentHistoryExtended_STND | INCIDENTID | = | Incident_Incidentdetails_STND | INCIDENTID |
...
Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)
Introducing a new dataset to capture Strategy Details data in Camms.Strategy
The Planning_StrategyDetails_STND dataset will allow you to capture data from the Strategy details page including extended fields such as Percent Completed, Status and Progress Comment.
...
Following are the fields included in the dataset:
Field name | Data type | Notes |
|---|---|---|
STRATEGYID | Unique identifier | This is a unique ID for each Strategy and you can use this to link with other datasets |
Title | Text | This field will retrieve the Title of the Strategy into your report |
Target Initiative | Text | This field will retrieve the Target Initiative of the Strategy into your report |
Status | Text | This field will retrieve the Status of the Strategy into your report |
Start Date | Datetime | This field will retrieve the Start Date of the Strategy into your report |
Secondary Agency | Text | This field will retrieve the Secondary Agency of Strategy into your report |
Responsible Person | Text | This field will retrieve the Responsible Person of Strategy into your report |
ref | Text | This field will retrieve the Reference of the Strategy into your report |
Progress Comment | Text | This field will retrieve the Progress Comment of the Strategy into your report |
Priority Criteria | Text | This field will retrieve the Priority Criteria of the Strategy into your report |
Primary Agency | Text | This field will retrieve the Primary Agency of the Strategy into your report |
Percent Completed | Numeric | This field will retrieve the Percent Completed of the Strategy into your report |
Other Agency | Text | This field will retrieve the Other Agency of the Strategy into your report |
Governance | Text | This field will retrieve the Governance of the Strategy into your report |
End Date | Datetime | This field will retrieve the End Date of the Strategy into your report |
Description | Text | This field will retrieve the Description of the Strategy into your report |
...
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 | Planning_StrategyDetails_STND | STRATEGYID | = | Planning_StrategyFilters_STND | STRATEGYID |
...
Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)
Introducing a new dataset to capture Strategy Filters data in Camms.Strategy
The Planning_StrategyFilters_STND dataset will allow you to report data from the Strategy details page tick boxes to filter out strategies.
Following are the fields included in the dataset:
Field name | Data type | Notes |
|---|---|---|
Title | Text | This field will retrieve the Title of the Strategy into your report |
STRATEGYID | Unique identifier | This is a unique ID for each Strategy and you can use this to link with other datasets |
Strategic Filter | Text | This field will retrieve the Strategic Filter option tick box value and you can use this to filter your report |
...
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 | Planning_StrategyFilters_STND | STRATEGYID | = | Planning_StrategyDetails_STND | STRATEGYID |
...
Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)
Modifications to the Planning_UserList_STND dataset to capture staff organizational link data for flex org hierarchy in Camms.Strategy
The modified Planning_UserList_STND dataset will allow you to capture staff orgnizational link data making it compatible with the flex org hierarchy data.
...