Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Camms is pleased to announce the September Feature Release for Camms.Insights

This was released on 19th September 2020 and includes the following new features and enhancements to improve your user experience within the system.

We are please to inform you that the Camms.Insights application is releasing an application upgrade with the September sprint with an enhanced user interface.

1. Proxima Nova replaces Roboto as default font

Proxima Nova will be the default font for new reports. Shown below is a comparison between the previous default font, and the new one.

Note: This will only be applied to newly created and existing reports which do not have specifically defined fonts.

2. The ‘Update Results’ button renamed as ‘Apply Filter’ with an additional button next to it to clear the filters

You will find the ‘Update Results’ button renamed as ‘Apply Filter’ and relocated to the filter area, to retain attention within the workflow.

Furthermore, you will find a new button named 'Clear Filter' next to the 'Apply Filter' button to clear all the filter values you have selected to filter the report by.

3. Export drill down grids at the current expansion level

When exporting a drill down grid, a message prompt will appear asking how you would like to export the report. 

Here, you will be given two options:

  1. Export with all rows as shown in viewer? – Selecting this option will export the report at the current expansion level in the report viewer.

  2. Export with all expanded records – Selecting this option will export the report with all the records expanded.

4. New conditional formatting options

You can apply conditional formatting on grids regardless of value. When setting conditional formatting, instead of specifying a Value, Value Range, or Percentage Range grids, you can now apply this setting to all values for that field.

Conditional formatting options are added to support bold, italic, and underline formatting for grids.

A new conditional formatting option for Horizontal and Vertical Grids, allowing conditional formatting to be applied to entire columns or rows in a grid.

5. Group value fields in a drill down grid

6. Images in the report header/footer will scale up/down to fit the container

  • Images you include in the report header/footer can now be formatted by defining the dimensions. If you tick the 'Constrain Proportions' tick box, the image will adjust in the header with it's original size.

  • If you need to change the size of the image, tick off the 'Constrain Proportions' tick box and define the dimensions as you need.

Note: Please note that in the reports which you have already designed, the size of the image will be set to 1*1 pixels by default, hence the image will not be visible in the report extracts. You will need to remove the image URL and insert it again to readjust the image.

7. Other general improvements

  • A change of the user interface in the data source area where you select the datasets for your report. A new section is included on top of the data source section for you to see the datasets you have selected along with a delete button to remove them easily too.

  • The formatting of the date columns are now ‘DateTime’ when exporting reports in Excel format.

  • To enable this feature in your report, you need to pick a format for your DateTime field

  • A new feature to keep grids expanded/collapsed by default.

  • You'll find a new separator type called, ‘Logical’ for pivot grids. This separator will block out data within the pivot, without creating a new grid instance, keeping all the data in-line.

  • Two additional tick boxes to select all the fields at once to be 'Visible' and 'Filterable' in the data model area

8. Enabling automatic creation of datasets for each custom hierarchy

This feature will allow you to create your own dataset for each custom hierarchy you configure in your system, which will support better performance and ease of reporting.

You can create datasets per each hierarchy configured in the Camms.Strategy application. In the 'Hierarchy Configuration' page in Camms.Strategy, you will see a button per each hierarchy to create the dataset. Once clicked, it will automatically create the dataset in your Camms.Insights application.

Each dataset you create will include the fields configured for the corresponding  along with the following.

Field Name

Data Type

Remarks

Hierarchy Name

Text

This denotes the name of the hierarchy

HIERARCHYID

Unique Identifier

This lets you uniquely identify each hierarchy

Hierarchy Description

Text

This field will display the description of the hierarchy

Hierarchy Type

Text

This field will retrieve the hierarchy type

To ensure this new dataset is enabled for use within your cammsinsights application, please follow the steps at the link below:
Administration: Configuring and enabling new datasets for use - Camms.Support Documentation - Confluence (atlassian.net)

9. Introducing a new dataset to display Authority Document and Incident linkages

The new Compliance_AuthorityDocumentIncidentLink_STND dataset will allow you to report on the linkages between Authority Documents and Incidents.

Fields included in the dataset are as below:

Field Name

Data Type

Remarks

Authority Document Title

Text

This denotes the title of the Authority Document

AUTHORITYDOCUMENTID

Unique Identifier

This lets you uniquely identify each Authority Document

Incident Title

Text

This denotes the title of the Incident

INCIDENTID

Unique Identifier

This lets you uniquely identify each Incident

To ensure this new dataset is enabled for use within your cammsinsights application, please follow the steps at the link below:
Administration: Configuring and enabling new datasets for use - Camms.Support Documentation - Confluence (atlassian.net)

10. Introducing a new dataset to display Policy and Incident Linkages

The new Compliance_PolicyIncidentLink_STND dataset will allow you to report on the linkages between Compliance Policies and Incidents.

Field included in the dataset are as below:

Field Name

Data Type

Remarks

Policy Title

Text

This denotes the title of the Policy

POLICYID

Unique Identifier

This lets you uniquely identify each Policy

Incident Title

Text

This denotes the title of the Incident

INCIDENTID

Unique Identifier

This lets you uniquely identify each Incident

To ensure this new dataset is enabled for use within your cammsinsights application, please follow the steps at the link below:

Administration: Configuring and enabling new datasets for use - Camms.Support Documentation - Confluence (atlassian.net)

11. Introducing a new dataset to display Compliance and Custom Hierarchy Linkages

The new Compliance_ComplianceCustomHierarchyLink_STND dataset will allow you to report on the linkages between Compliance Requirements and Custom Hierarchies.

Fields included in the dataset are as below:

Field Name

Data Type

Remarks

Compliance Title

Text

This denotes the title of the Compliance

COMPLIANCEID

Unique Identifier

This lets you uniquely identify each Compliance

Hierarchy Name

Text

Name of the hierarchy

HIERARCHYID

Unique Identifier

This lets you uniquely identify each Hierarchy

Hierarchy Node

Text

Name of the hierarchy node

Hierarchy Node Level

Text

The level of the corresponding hierarchy node

To ensure this new dataset is enabled for use within your cammsinsights application, please follow the steps at the link below:

Administration: Configuring and enabling new datasets for use - Camms.Support Documentation - Confluence (atlassian.net)

12. Modification to the Risk_ProjectRiskRevised_STND dataset to display Monte Carlo Analysis data

The Risk_ProjectRiskRevised_STND dataset will be modified to support the new Monte Carlo Analysis feature introduced in Camms.Risk.

New fields included in the dataset are as below:


Field Name

Data Type

Remarks

Best Case Scenario ($)  

Integer Numbers  

Quantitative Range Assumptions for Best Case Scenario  

Text

Most Likely Scenario ($) 

Integer Numbers 

Quantitative Range Assumptions for Most Likely Scenario 

Text

Worst Case Scenario ($) 

Integer Numbers 

Quantitative Range Assumptions for Worst Case Scenario 

Text 

Likelihood 

Numeric 

P10 Projection 

Integer Numbers 

P50 Projection 

Integer Numbers 

P90 Projection 

Integer Numbers 

  • No labels