Camms is pleased to bring you the Quarterly Product Release Note for Camms.Risk Compliance Management.

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 11th March 2023 and will be available in your Live environment on 25th March 2023.


List of items

1. Improvements to the Add New icon in the left-hand menu.

2. Introduction of Read-Only feature to Compliance/Obligation, Authority Document, and Policy workflows

3. Improvements to the Linkage Object

4. Improvements to the filters in the Compliance Settings page


1. Improvements to the Add New icon in the left-hand menu.

This feature will allow the users to configure Compliance, Authority Document and Policy wise register groupings within the Add New icon in the Left-Hand Side Quick Access Menu. 

How do you configure this?

  • A Compliance Type should be created or should be available with the ‘Visible in Add New’ option ticked under 'Menu > Compliance Settings > Obligation Type'.
  • An Active Compliance Register should be created or should be available under 'Menu > Compliance Settings > Register Configuration'.
  • A Register Group/Groups should be created or should be available under 'Menu > Compliance Settings > Register Grouping Configuration'.

Note: Similarly, this can be configured in all 3 Compliance, Authority Document and Policy modules.

How does this work?

  • Upon clicking the Compliance, Authority Document, and Policy types configured within the Register grouping, the user will be directed to the relevant detail page for the respective record creation.
  • A default Register grouping will be displayed if no specific Register grouping is configured.


2. Introduction of Read-Only feature to Compliance/Obligation, Authority Document, and Policy workflows

A read-only feature will be introduced to Compliance/Obligation, Authority Document, and Policy workflows. This modification is applicable to those using integration for Compliance record creation, where records can be left as Read-Only and un-editable if received via an Integration, marked as ‘Read Only’. 

This functionality is already applied to the standard ‘ComplianceObject’ in the Compliance Workflow and will now be expanded across the entire Compliance application, which includes Compliance, Authority Document and Policy. 

This will apply to both standard and custom objects except Linkage, Document, Task, Actions, and Controls objects.

Furthermore, a new setting 'Override Read-only Feature' will be introduced, allowing you to override the Read-Only feature and make the required fields as editable, if required.

How do you configure this?

new setting called 'Override Read-only feature' will be introduced within Object Configuration, letting you override any required fields. This can be configured via Mega Menu > Framework > Compliance Settings > Object Configuration > Select a specific Object. 

Note: By Default, this setting will be set to ‘False’ (Unticked)


How does this work?

If the above setting is enabled for a particular field, the Read only functionality for the record will be overridden and the specific field will be made editable within the record. 


3. Improvements to the Linkage Object

The 'Add New' button in the Linkage object and field wise links button, will be made consistent with the Document and Action objects. It will be placed at the center of the Linkage grid, when in an empty state, and at the top-right corner when there are records available within the grid. 

Figure 3.1: Add New button alignment in Linkage Object at empty state

Figure 3.2: Add New button alignment in Linkage Object with records


4. Improvements to the filters in the Compliance Settings page

The filters within the Compliance Settings pages accessed via Mega Menu > Framework > Compliance Settings will be simplified to only have the ‘Contains’ search filter. This will allow users to easily filter the required details.

Note: This will only be applicable to the main settings and not for any additional grids within the settings

Figure 4.1: Filters in Compliance Settings


Additional Note: Click here to view a list of issues that we are currently aware of and working to resolve.

Known Issues