Overview

Compliance settings is the key configuration area of the Camms.Risk Compliance system where an administrator can configure each of the windows displayed for users. You can access Compliance Settings via Menu > Framework > Compliance Settings. 

Each of the compliance setting section will let you select the register type from Compliance, Authority Document, or Policy Registers to which you make the changes to.

Note: All configurations will have the same behaviour for either register type you chose from.

This section comprises all the administrative functions related to compliance management. This will enable the client administrator to configure the Compliance, Authority Document, and Policy Management Process workflow as required for the organisation.

The following incident settings will be available to be configured:

  • User
  • User Roles
  • Standard Roles
  • Location
  • Priority
  • Severity
  • Likelihood
  • Risk Rating Type
  • Risk Rating Calculation
  • Review Frequency
  • Causes and Consequences
  • Code Setup
  • Lists
  • Custom Tables
  • Display Texts
  • Object Configuration
  • Register Configuration
  • Register Grouping Configuration
  • Workflow Configuration
  • Incident Type
  • Category
  • Task
  • Notification Templates
  • Notifications
  • Object Section Configuration
  • Portal Configuration
  • Incident Type Group Configuration
  • Miscellaneous Settings
Note: This module will only be available to the clients who have purchased Camms.Risk Compliance.


User Settings

This settings page will let you view a list of all users for a register type in the system. You can select a user and allocate one or more user roles to provide them with required permissions. You cannot create or remove users from this screen, that can be done under Administration > Manage Users.

To assign user roles to a user:

  • STEP 1: Navigate to Framework > Compliance Settings > User.
  • STEP 2: Click on the relevant username.

This will display the user details including Username, Salutation, a checkbox to make the user Active, and User Roles.

  • STEP 3: Select user roles from the User Roles list.
    All user roles setup via the User Roles page will be displayed here. Multiple user roles can be assigned to one user.
  • STEP 4: Click on the 'Save' button to save details.
     

User Roles Settings

This settings page will let you view a list of user roles for a register type within the system and update its workflow and permissions here. Additionally, you can create custom user roles too. These roles can be assigned to individual users within the User settings area.

To add a new user role:

  • STEP 1: Navigate to Framework > Compliance Settings > User Roles.
  • STEP 2: Select one of the register types from the Register Type dropdown.

This will display the user role details page for the selected register type when adding a new user role.

  • STEP 3: Click on the 'New' button at the top-right corner of the window.
  • STEP 4: Enter the user role details.

Field

Description

Role Name

Define a name for the user role.

Description

Define a description for the role.

Workflow

Select a workflow to provide access levels to the workflow.

User roles are workflow based.

Note: The workflows will be listed as per the selected register type from the Register Type dropdown.

Permission

Ticking on a permission enables you to setup different permission access to the user role.

Note: Please refer the below Permission section to explore more.

Permission

The following permissions are available.

Tick on the permission to grant the access to the relevant area/setting.

Standard Permissions

  • Standard Compliance Add Permission: This permission will let you add a compliance.
    Note: It is recommended not to use the above permission for any user roles created.
  • Display all records in registers: This permission will let you view details of a particular incident only if it has the authorisation to see the incident title in the register. Recommended only for administrators.
    • Tick this option to permit the user role to view all details and records in their register (including the users with no ‘View’ permission).
    • Untick this option to restrict and hide details and records of registers for users with no ‘View’ permission.
      Note: The standard user roles will have this permission as default, enabling to view all incident records of the register for which they are responsible.
  • Standard Unlock All Objects In Compliance Drafts For Editing Permission: This permission will let the user make changes to all objects in compliance drafts.
  • User Settings: This permission provides access to the Compliance Settings > User setting. Recommended only for administrators.
  • User Roles Settings: This permission provides access to the Compliance Settings > User Roles setting. Recommended only for administrators.
  • Standard Role Settings: This permission provides access to the Compliance Settings > Standard Roles setting. Recommended only for administrators.
  • Location Settings: This permission provides access to the Compliance Settings > Location setting. Recommended only for administrators.
  • Priority Settings: This permission provides access to the Compliance Settings > Priority setting. Recommended only for administrators.
  • Severity Settings: This permission provides access to the Compliance Settings > Severity setting. Recommended only for administrators.
  • Likelihood Settings: This permission provides access to the Compliance Settings > Likelihood setting. Recommended only for administrators.
  • Risk Rating Type Settings: This permission provides access to the Compliance Settings > Risk Rating Type setting. Recommended only for administrators.
  • Risk Rating Calculation Settings: This permission provides access to the Compliance Settings > Risk Rating Calculation setting. Recommended only for administrators.
  • Category Settings: This permission provides access to the Compliance Settings > Category setting. Recommended only for administrators.
  • Code Setup: This permission provides access to the Compliance Settings > Code Setup setting. Recommended only for administrators.
  • List Item Configuration: This permission provides access to the Compliance Settings > List Item Configuration setting. Recommended only for administrators.
  • Display Text Settings: This permission provides access to the Compliance Settings > Display Text setting. Recommended only for administrators.
  • Object Configuration Settings: This permission provides access to the Compliance Settings > Object Configuration setting. Recommended only for administrators.
  • Register Configuration Settings: This permission provides access to the Compliance Settings > Register Configuration setting. Recommended only for administrators.
  • Workflow Configuration Settings: This permission provides access to the Compliance Settings > Workflow Configuration setting. Recommended only for administrators.
  • Type Configuration: This permission provides access to the Compliance Settings > Type Configuration setting. Recommended only for administrators.
  • Email Notification Settings: This permission provides access to the Compliance Settings > Email Notifications setting. Recommended only for administrators.
  • Miscellaneous Settings: This permission provides access to the Compliance Settings > Miscellaneous setting. Recommended only for administrators.
  • Custom Table Settings: This permission provides access to the Compliance Settings > Custom Tables setting. Recommended only for administrators.
  • Display Alert Register: This permission provides access to display the alert register within a compliance.
  • Add / Edit / Delete Alert Details: This permission provides access to the add/edit/delete details of an alert.
  • Review Frequency Settings: This permission provides access to the Compliance Settings > Review Frequency setting. Recommended only for administrators.
  • Dashboard Configuration Settings: This permission provides access to the Compliance Settings > Dashboard Configuration setting. Recommended only for administrators.
  • Register Grouping Configuration: This permission provides access  to the Compliance Settings > Register Grouping Configuration setting. Recommended only for administrators.
  • Type Group Configuration Settings: This permission provides access to the Compliance Settings > Review Frequency setting. Recommended only for administrators.

STEP 5: Click on the 'Save' button at the top-right corner to save details.


Standard Roles Settings

This settings page will let you view a list of standard record field inherited roles for a register type within the system and update which user roles it is attached to. These inherited roles get automatically assigned to users based on the criteria for that role – this will apply only to the record in question (e.g. Users who create a new record would automatically inherit the Creator role permissions for that record). Additionally, create new inherited roles within this page and specify which workflow, object, and field it applies to. 

The following standard roles will be offered by default for the three registers:

  • Compliance Register
    • Compliance Action Responsible Officer
    • Compliance Creator
    • Compliance Responsible Officer
  • Authority Document Register
    • Authority Document Action Responsible Officer
    • Authority Document Creator
    • Authority Document Responsible Officer
  • Policy Register
    • Policy Action Responsible Officer
    • Policy Creator
    • Policy Responsible Officer

You need to assign which user roles (created under Compliance Settings > User Roles) will apply to these pre-defined standard roles; thereby assigning users selected in staff dropdowns in fields, when creating compliance records.

To assign user roles for pre-defined standard roles:

  • STEP 1: Select a 'Register Type' from the dropdown and click on a pre-defined standard user role.
  • STEP 2: Select which 'User Roles' will be associated with this standard role, thereby defining the permissions.
  • STEP 3: Click on the 'Save' button at the top-right corner of the window to save details.

In the situation where a staff member does not fall under the user roles defined in the pre-defined set of standard roles, and requires limited or certain amount of access to a compliance document to view in their registers, this can be done by creating a new Standard Role.

To add a new standard role:

  • STEP 1: Select a 'Register Type' from the dropdown and click on the 'add' button at the top-right corner of the window.
  • STEP 2: Enter a user 'Role Name' and a 'Description' for the user role.
  • STEP 3: Select the 'User Roles' you wish to define the permission level for the user to access.
  • STEP 4: Select the 'Workflow' that will apply for this user.
  • STEP 5: Select the 'Object' that you want the permit this user access with.
  • STEP 6: Select the 'Field' of the object that is related to this user.
  • STEP 7: Click on the 'Save' button at the top-right corner of the window to save details.


Location Settings

This settings page will let you define a list of locations for a register type, along with its latitude and longitude coordinates, to be shown within the Location field when creating a new compliance record.

To add a new location:

  • STEP 1: Navigate to Framework > Compliance Settings > Location.
  • STEP 2: Select one of the register types from the Register Type dropdown.
    This will display the location details page with the selected register type as the default selection, when adding a new location.
  • STEP 3: Click on the 'Add' icon at the top-right corner of the window.
  • STEP 4: Enter the location details.
    Define a name, description, latitude, and longitude for the location.
Note: The locations entered here will appear in the location dropdown within the details page.
  • STEP 5: Click on the 'Save' button to save details.


Priority Settings

This settings page will let you define the standard list of compliance priority tags for records of a register type, to be showing within the Priority field, and set its colour (to be shown in the register), image, and weightage value (for risk rating calculations).

To add a new priority level:

  • STEP 1: Navigate to Framework > Compliance Settings > Priority.
  • STEP 2: Click on the 'New' button at the top-right corner of the window.
  • STEP 3: Fill in the relevant fields.

Field

Description

Priority Name

Define a title for the priority value.

Description

Enter a description.

Image 

Upload an image for the priority value. The maximum size of the image should not exceed 2KB.

Choose Priority Level Colour

Choose a colour from the colour picker to represent the priority value.

Priority Weightage

Define a weightage for the priority value.

  • STEP 4: Click on the 'Save' button to save details.


Severity Settings

This settings page will let you define the standard list of severities for records of a register type, to be showing within the Severity field, and set its colour (to be shown in the register), image, and weightage value (for risk rating calculations).


To add a new severity level, follow the below steps:

  • STEP 1: Navigate to Framework > Compliance Settings > Severity.
  • STEP 2: Click on the 'New' button at the top-right corner.
  • STEP 3: Fill the relevant fields.

Field

Description

Severity Name

Define a title for the severity level

Description

Enter a description

Image 

Upload an image for the severity level. The maximum size of the image should not exceed 2KB

Choose Severity Level Colour

Choose a colour from the colour picker to represent the Severity level

Severity Weightage

Define a weightage for the severity

Severity Sort Order

The defined severities will be sorted by the order mentioned here in the dropdowns 

  • STEP 4: Click on the 'Save' button to save details.


Likelihood Settings

This settings page will let you define a list of likelihood ratings to be used for risk ratings, and set its colour (to be visible in the register), image, and weightage value (for risk rating calculations).

To add a new Likelihood value:

  • STEP 1: Navigate to Framework > Compliance Settings > Likelihood.
  • STEP 2: Click on the 'New' button at the top-right corner of the window.
  • STEP 3: Fill the relevant fields.

Field

Description

Likelihood Name

Define a title for the Likelihood values.

Description

Enter a description.

Image 

Upload an image for the likelihood values. The maximum size of the image should not exceed 2KB.

Choose Likelihood Level Colour

Choose a colour from the colour picker to represent the Likelihood values.

Likelihood Weightage

Define a weightage for the likelihood values.

Likelihood sort order

The defined likelihood values will be sorted by the order mentioned here in the dropdowns.


  • STEP 4: Click on the 'Save' button to save details.


Risk Rating Type Settings

This settings page will let you define a list of risk rating types for a register type, to categorise a record by and set its colour (to be visible in the register), image, weightage value (for future calculations), and min/max values.

To add a Risk Rating Type:

  • STEP 1: Navigate to Framework > Compliance Settings > Risk Rating Type.
  • STEP 2: Click on the 'New' button at the top-right corner of the window.
  • STEP 3: Fill in the relevant fields.

Field

Description

Risk Rating Name

Define a title for the Risk Rating values.

Description

Enter a description.

Image 

Upload an image for the Risk Rating values. The maximum size of the image should not exceed 2KB.

Choose Risk Rating Level Colour

Choose a colour from the colour picker to represent the Risk Rating values.

Risk Rating Weightage

Define a weightage for the Risk Rating value.

Risk Rating sort order

The defined risk ratings values will be sorted by the order mentioned here in the dropdowns.

  • STEP 4: Click on the 'Save' button to save details.


Risk Rating Calculation Settings

This settings page will let you define the formula to generate the risk rating (e.g. (L*S), (L+S)) for a register type. Use L = Likelihood, S = Severity along with standard mathematical operators: +, -, *, /, ().  Currently, this applies only for calculations using the Severity (S) and Likelihood (L) values.

Click on the 'Save' button once entered the formula to save details.

Note: This will only work for calculations using the Severity and Likelihood values, which is used as the notations S and L respectively. This will support simple calculations like (L*S) or (L+S).


Review Frequency Settings

This settings page will let you define the different review frequency options for records in a register type, which will be displayed in the Review tab. Set an image, colour (to be visible in registers), position of the field in the review tab, frequency type and type count (how many times it will be reviewed for the selected type), and how the next review date should be determined (a specific day or end of that period). 

  • STEP 1: Navigate to Framework > Compliance Settings > Review Frequency.
  • STEP 2: Select the Register Type.
  • STEP 3: Click on the 'New' button to add a new frequency type, or click on an existing value to edit it.

Field

Description

Review Frequency Name

Define a title for the review frequency name.

Description

Enter a description.

Image 

Upload an image for the review frequency value.

Colour

Choose a colour from the colour picker to represent the frequency value.

Position 

Define a position the specific value is going to be placed in the review frequency dropdown, in the Review tab.

Type 

Define the type of the review frequency. Options are:

  • Year – Will relate the review frequency value as a yearly count.
  • Month – Will relate the review frequency value as a monthly count.
  • Day – Will relate the review frequency value as a daily count.

Count 

The count of the above selected type the value should be accounted for. 

E.g. If Yearly was selected as the type, and '2' was selected as the count, the frequency of the value would be counted as bi-annually by the system.

Set next review date for the period

Define how the next review date for the period is set. Options are:

  • Select the Day for the period – If this is selected, a specific day from the below option should be selected. E.g. If the type was set as Monthly, a day from the month (say 15) can be selected to define the monthly review date. And it will be set to the 15th of each month.
  • End of the period – If this is selected, the review date will be set to the end of the period. If the type was set as Monthly, the end of the month will be set as the next review date at each review cycle.

Day

Set the day as per the above configuration.


Code Setup Settings

This settings page will let you define how the record code numbering sequence is setup for register types. You may setup different numbering based on incident types, selecting the numbering sequence, adding a prefix/suffix or mask as required, defining a start number and entering a group name for generic incident code types to have its own numbering system.

  • STEP 1: Navigate to Framework > Compliance Settings > Compliance Code.
  • STEP 2: Select the Register Type.
  • STEP 3:  Select a Numbering Sequence. Three options are available.
None: Selecting 'None' will leave the number sequence empty. When a new compliance is created, no automatic number will be assigned and the user will have to manually enter a number.
  • Strict Sequential Numbering: Selecting this option will automatically populate a sequential number for new compliances created. The number will be non-editable by the users.
  • Editable Sequential Numbering: Selecting this option will automatically populate a sequential number for new compliances created. This will be editable in order for the user to change the number, if required.
  • STEP 4: Enter a 'Prefix' for the code.
  • STEP 5: Enter a start number for the compliance code. Once you add a start number, any compliance created will be assigned a number starting from the number specified. Furthermore, the functionality of the number will be based on the numbering sequence option selected.
    Notes:
    • Additionally, you can enter a mask for the code. This would mean that you can add a mask as 0000 and the codes will begin and end with 0001 and 9999. 
    • When Codes are set to be identified against a type, each configuration per compliance, authority document, or policy type, will be displayed in the grid below the area.
  • STEP 6: Enter a 'Suffix' for the code.
  • STEP 7: Click on the 'Save' button at the top-right corner of the window to save details.


Lists Settings

This settings page will let you define single-select or multi-select dropdown lists and its values to be used within different objects in register types of a workflow. Do not leave spaces when creating a list name. Click into a list name to setup the options to be listed for that item, along with how they should be sequenced, which is the default value and inactivate options that is no longer relevant.

To add a new list item:

  • STEP 1:  Click the 'New' button at the top-right corner of the window.
  • STEP 2: Enter a name for the list along with a description. Ensure that the list name doesn’t have any spaces in-between.
    Eg: 'ReportedTo' or 'Reported_To' instead of 'Reported To'

  • STEP 3: Define the list values from the ‘Values’ area below by clicking on add new.

Field

Description

Name

Define a title for the list value

Description

Enter a description

Value Sequence 

The sequence in which the configured list value should appear in the dropdown (list fields)

Active

Whether the list value is active. Only active ones will be shown for the end user in the dropdowns (list fields)

Default

Whether the list value should be the default selection for the list field 

Image 

Upload an image for the Risk Rating values. The maximum size of the image should not exceed 2KB

Choose value Level Colour

Choose a colour from the colour picker to represent the list values 

Value Weightage

Define a weightage for the list value 

Value Min Value 

Define the minimum value for the list value.

Note: This is only applicable if you have the survey integration.

Value Max value 

Define the maximum value for the list value.

Note: This is only applicable if you have the survey integration.

Note: If required, additional properties can be configured for each list in the system using the ‘Properties’ option. This can be used to define information about the list such as ID, Dates or any other details.
  • STEP 4: Click on the 'New' button.

Field

Description

Property Name

Define a title for the property.

Field Type

Select from a list of field types the type of field the property is going to be. The same set of field types explained under Framework > Compliance Settings > Object Configurations will be shown here as well.

Label Reference 

Define a label for the property.

Property Configuration Sequence

The sequence in which the property should appear in the grid.


Custom Tables Settings

This settings page will let you define custom tables to be used within different objects of register types of a workflow. Do not leave spaces when creating table names. Click into a table name to add columns to the table. A preview of the table will be displayed at the bottom of the page and if this table needs to be pre-populated with a list of rows as a template, that can be setup here.

To create a new custom table:

  • STEP 1: Enter a name for the table along with a description. Ensure that the table name doesn’t have any spaces in-between.
    E.g. 'WitnessDetails' or 'Witness_Details' instead of 'Witness details'

  • STEP 2: Click 'Save'.
Note: If you have deleted the custom table, the ‘Deleted’ checkbox will be ticked.

Once you click on 'Save' you will get a table view as below which allows you to enter column values. 

Click on the 'New' button to add column values. These will be the columns of your table. 

  • STEP 3: Enter a set of columns for the table. 
  • STEP 4: Enter sequence in which the columns should appear.
  • STEP 5: Click 'Save' at the top of the column grid.
Note: A preview of the configured custom table and show it is shown for the end user is available below under ‘Custom Table Default Template’ area. The administrator can have a view of the end user view for the custom tables they construct from here.


Display Text Settings

This settings page will let you define display text to be used within register type objects of a workflow for various labels according to the requirements of your organisation. Include help text, placeholder text, validation error text, and the plural form of the text. Additionally, the main display text can be directly edited within the relevant field in the Object Configuration section for your convenience. Therefore, you will not require to access this page for a simple display text change. However, for configuring additional attributes like the placeholder text, will require to be done from this screen.

To create a new Display Text:

  • STEP 1: Select a Register form the ‘Register Type’ dropdown.
  • STEP 2:  Click the 'New' button at the top-right corner of the window.
  • STEP 3: Enter the Label reference which will create reference point. Ensure that the label reference doesn’t have any spaces in-between.
    E.g.: 'ReportedTo' or 'Reported_To' instead of 'Reported To'
  • STEP 4: Enter the Tool tip and the display text. Display text entered here would be the text displayed in the label across the application.

Field

Description

Label Reference 

The label reference for the display text to be created 

Display Text

Define the display text. This will be the text used for the field across the application 

Help Text 

The hover over help text for the field to be configured from here

Placeholder Text

For any text fields, the placeholder text (ex: Please enter your name here’ to be defined here

Validation Error Text 

Define the text to be used for the display text item in validation messages 

Plural Display Text 

Define the plural text for the display text configured 

  • STEP 5: Click 'Save'.


Object Configuration Settings

This settings page will let you configure fields in various register types, for its standard and custom objects used in a workflow. Custom fields can be created for standard objects if required. Additionally, define if objects require a sign-off or approval, its visibility, display in My Quick Updates, and more. Furthermore, within an object you can define a field’s label, visibility, sequence, and mandatory state.

There are seven standard objects within the system:

  • Compliance Object – This object will enable configuring the field available within Compliance details page which the user will see when they enter a new compliance record. This will contain the preliminary information about the compliance.
  • Action Object – This object will enable configuring the fields available in the action page. Action page is where the user will enter information about action that is linked to a compliance.
  • Review Object – This object will enable configuring the fields available within review page, Review page is where the user will enter data on reviews of the compliance
  • Document Object – This object will enable configuring the documents page. This page will allow users to upload any documents or add any URL to the compliance. You will not be able to configure any fields within this page.
  • Linkages Object – This object will enable configuring the linkages page. This page will allow users to link an incident to a risk, project or a hazard. You will not be able to configure any fields within this page.
  • Risk Analysis Object – This object will enable configuring the fields available within Risk Analysis page
  • Root Cause Analysis Object – This object will enable configuring the fields available within Root Cause Analysis Object page.

Click on the object name to go into the respective configuration page. All standard objects will be listed here by default. Any new custom objects can be created from here as well.

To create a new Object, follow the steps below:

  • STEP 1: Navigate to Framework > Compliance Settings > Object Configurations
  • STEP 2: Click on the 'New' button.
  • STEP 3: Enter all relevant information and configure the fields. More information on configurations are given below.
  • STEP 4: Click on the 'Save' button to save details.

Changing the description will change the display text of the corresponding page.

  • Standard Object – The objects that are standard will have the standard object tick box checked. This cannot be edited by the Client administrator.
  • Enable Sign Off – This field will enable the sign off functionality for the corresponding object. Signoff functionality will not be available for linkages, actions and document objects.
  • Visible – This field can use to determine if the object appears for the end users in the compliance workflow or not. For the object to appear, the visibility should be turned on.
  • Enable Submit – This is used to determine whether the submit option for the record should be placed on the object or not. The same applies to the Enable Re-Submit button as well.
  • Show in My Quick Update – This will determine if the contents of the object are to be shown in the My Quick Update area. This is only applicable to Compliance, Policy, Authority Documents, Actions and Review objects only. 
  • Enable Approval – This can be ticked if you require an approval in the workflow for an object, then enable this tick box for only ONE object. This will then configure this feature for all objects in that workflow.
    Note: When configuring the Enable Approval setting, it should be set for ONLY ONE object in a workflow (eg: close object, incident object). If not, this setting would not function as expected.

    However, for an Action Object, the enable approval configuration can be set separately, in addition to other workflows. In a future release, Camms will look into making this process more user-friendly.

  • Show Action Progress Updates – This can be ticked if you wish to periodically review recurring and non-recurring compliance actions with progress update information. This will enable a two tab view within the action object: Action Details, Action Progress Update. (See section Periodic Reviews for Compliance Actions under Action in Compliance Management.)

Note: Enable Investigation Submission and Enable Approvals options are non-functional at the moment. 

The grid at the bottom of the page will allow the administrator to configure fields within the object. Following columns will be available.


Column

Description

Field Name

Enter a field reference name for each field. Ensure there are no spaces in the field name defined.

Note: To include single select/ lists and custom tables, you must enter the exact name entered within List items/ Custom tables for the equivalent field as the field name.

Field Type

Select the field type you want to add from a list of types. Following field types are available.

  • Checkbox – Checkbox field.
  • Compliance Status Name dropdown 
  •  Custom Multiselect – Custom multi select dropdowns. Ensure that this type is used with a field reference to a multi select list item configured through list item area.
  • Custom Single select – Custom dropdowns. Ensure that this type is used with a field reference to a single select list item configured through list item area.
  • Custom Radio button – radio buttons
  • Custom table- Custom table. Ensure that this type is used with a field reference to a custom table configured through custom tables’ area.
  • Date Picker – a date picker field 
  • Date Time Picker – Date and time picker 
  • Group Header – a heading field 
  • Hierarchy Links – a button with the organisation hierarchy pop up for easy linkage creation 
  • Multiline Textbox –Text and numeric field. Multiline.
  • Numeric Textbox – Numeric only field.
  • Authority Document Status Name dropdown – a dropdown listing status names for ADs
  • Policy Status Name dropdown – a dropdown listing status names for policies
  • Rich-Text Editor 
  • Staff Dropdown – Dropdown field listing all staff names. Single select.
  • Staff Multi select – Dropdown field listing all staff names. Multi select.
  • Textbox – Text and numeric field. Single line.
Note: Only the recommended and implemented field types are mentioned here.

Label Reference

A list of label references defined through display text will be available. You can select the reference of the label that the field should refer to.

Standard field

Indicates whether the field is a standard or a custom field. System administrator will not be able to remove the standard fields in the system.

Visible

You can toggle the visibility of the field by selecting true/false from this column.

Sequence

Sequence of which the fields will be displayed in the page.

Is decision point

Define whether the field is a decision point to determine with rest of the workflow based off on selections made from the field.

Note: This is only applicable for list type fields (custom/multi select fields and radio button fields).

Is Required In Save

Define whether the field configured is required to have data entered when attempting to save. If the field is not filled in, the system will notify the users upon clicking on save via a validation message

Is Required In Submit

 

Define whether the field configured is required to have data entered when attempting to submit. If the field is not filled in, the system will notify the users upon clicking on submit via a validation message

Visible In Mobile

 

Define whether the field configured should be visible in the mobile application.

Note: This is only applicable for the implemented fields supporting the mobile application.

Required For Integration

Define whether the field configured is a must for integration packages configured 

Is Enable Document Attach

Enable an attach document button for the field

Is Linkage Enable

Enable a create linkages button for the field 

Is Organisational link Enable

Enable the option to create a linkage to the organisation hierarchy only, for the field 

Is Action Creation Enabled

Enable a create actions button for the field 

Show In My Quick Update

Define if the field is to eb shown in the My Quick update.

Note: This is only applicable for implemented fields from Compliance, Authority Document, Policy, Review and Actions objects.

Override Compliance Read Only Permission

When the objects are marked read only for all users from integration, this would define if the field can override that permissions and should be editable.

Note: Only applicable for the integration.

To add a new field, follow the steps below:

  • STEP 1: Navigate to Framework > Compliance Settings > Object Configurations.
  • STEP 2: Click on the 'New' button at the top of the field grid.
  • STEP 3: Enter a field reference and configure other columns as required.
  • STEP 4: Click on the 'Save' button to save details.

The following standard fields are available for each standard object.

Compliance Register to be selected from Register Type.

Field Reference

Type

Description

Mandatory/Optional

Compliance Details Object

Ref

Text box

 

 

Compliance Code

Text box

Code of the compliance. The code can be configured by Incident code setup within compliance settings.

Mandatory

Compliance Title

Textbox

Title of the Compliance.

Mandatory

Compliance Type

Custom Single Select

The type of the Compliance. The dropdown will list all types of Compliance entered through compliance type within compliance settings. The selection will determine the workflow of the Compliance.

Note: The sequence of the ‘Compliance Type’ field should always be before any other field. This is to ensure when a compliance is created, the 'Type' is identified and thereafter the respective fields load based on that Type.

Mandatory (can be changed to optional)

Compliance Responsible Officer

Staff Dropdown

Responsible officer of the Compliance. This field will determine the user who will have access to the compliance through My Quick update> My compliances

Mandatory (can be changed to optional)

Compliance Description

Multiline Textbox

Add a description to the compliance.

Mandatory

Compliance Reported Date

Created Date

Date that the compliance is reported.

Mandatory (can be changed to optional)

Compliance Reported By

Staff Dropdown

The staff who reported the compliance. 

Mandatory (can be changed to optional)

Compliance Status Name

Custom Single Select

The Status of the Compliance.

Mandatory (can be changed to optional)

Compliance Category Name

Custom Multi Select

Category of the Compliance

Mandatory (can be changed to optional)

Compliance Parent

Parent Child Cascade List

 

Mandatory (can be changed to optional)

Is Active

Check Box

                

Mandatory (can be changed to optional)

Action Object

Action Name

Text Box

Action title

 

Action Type
Check Box
If the ticked, it would mean the action is a recurring action. If it is left unticked it would mean it would be a non recurring action.

Responsible Officer

Staff Dropdown

Staff member who is responsible for the action. This field will determine the user who will have access to the action through My Quick Update > My Actions.

 

Status

Incident Action Type

Status dropdown. Options available; Not started, in progress, completed, deferred, ongoing.

 

Start Date

Date Time Picker

Start date of the action.

 

End Date

Date Time Picker

End date of the action.

 

Percent Completed

Integer Text Box

Completion % of the action.

Setting a status of 'Not Started' will set the % complete to 0.

Setting a status of 'In progress' will allow the user to enter % complete between 1-99

Setting a status of 'Completed' will set the % complete to 100.

 

Description

Multiline Text Box

Description of the action.

 

Comment

Multiline Text Box

Enter progress comments for the action.

 

Actual Completion Date

Date Time Picker

Enter the actual completion date of the action. This may differ from the end date.

 

Review Object

Review Compliance Title

Compliance Code And Title

Title of the Review compliance & the code

 

Review Frequency

Review Frequency Type Dropdown          

This defines how frequent the review should be carried out

 

Last Reviewed By

Last Reviewed By                

The Name of the Individual who carried out the last review

 

Last Reviewed Date

Last Reviewed Date Time Picker

The date on which the last review was carried out

 

Next Review Date

Next Review Date Time Picker

The date on which the next review is scheduled to be held

 

Compliance Review Status

Text Box

Status of the Compliance 

 

Review Comment

Review Comment

The comment regarding the review

 

 

Unique Details Object

In addition to the seven standard objects within the system (including the standard ‘Compliance Details’ object which is a common configuration), users are able to create and maintain a unique version of the standard ‘Compliance Details’ object.

The fields, field labels and field positions can be identified distinctively per workflow with this set up as opposed to using the standard common configuration which will be common across all workflows.

To set up this function:

  • STEP 1: Select ‘Compliance Details’ from the Workflow Element Type dropdown when creating the new Object.
  • This will auto-populate a copy of the existing standard incident details object with all its fields.
  • STEP 2: Define the fields with their properties in the field configuration area.
  • STEP 3: Click on the 'Save' button to save the details.


Register Configuration Settings

This settings page will let administrators configure the different registers and its fields of register types. Define how incident types should be grouped in registers and set additional attributes like which field in the register acts as the hyperlink to open the record, fields to be shown, the sequence, and whether it appears in the register search. If you use the Portal feature, the visibility and searchability in the portal can be defined too.

To add a new Register follow the steps below:

  • STEP 1: Navigate to Menu > Framework > Compliance Settings > Register Configuration.
  • STEP 2: Click on the 'New' button.
  • STEP 3: Fill the relevant fields defining the properties of the register.

The following fields will be available:

Column

Type

Description/Instructions

Mandatory/Optional

Register Name

Text

Name of the register

Note: This name will be used on the homepage area and menus for the new registers.

Mandatory

Description

Text

A short description defining the register

Optional

Compliance Type

Multi-Select Drop down

Lists all the Compliance types configured in the application.

Note: Users will be able to select one/more compliance types to sit within each new register created by ‘Compliance Type’ dropdown. Users can choose to have separate registers for each/multiple/all compliance type/s.

Mandatory

Register Type

Single-Select Drop down

Select the register type from the dropdown.

Optional

Active

Tick box

Determines whether the register is Active or Inactive.

Optional

Show in Home Page

Tick box

Determines whether the newly created register appears on the homepage.

Optional

Field to be hyperlinked 

Single-Select Drop down

Determines which field out of code or title should be the hyperlink in the register 

Optional

Sequence 

Numeric text box

The order in which the register should appear on the register home page

Optional

  • STEP 4: Click on the 'Save' button to save the details.

All the list of ‘Active’ registers created will be able to access via the Menu and the left side navigation. A new navigable link will be created for all newly created registers under Compliance Management which are made ‘Active’.

The register field configuration area will show all standard and custom fields for the workflow and the user will be able to select any field required and activate them to be shown in the register and register filters.

The grid which will appear upon saving configuration will have the below features:

  • Visible   Once ticked the field will appear as a column in the register.
  • Visible in Portal   Once ticked the field will appear as a column in the incident portal.
  • Searchable in Portal   Once ticked the field will appear as a filter in the register.
  • Searchable Once ticked the field will appear as a filter in the register.
  • Sequence   The position in register and portal to be set via sequence.
  • Width   The column width in register and portal to be set via width.

Note: When setting Responsible Officer and Secondary Responsible Officer fields of registers, set the 'Responsible Officer Dropdown' field type only for the Primary Responsible Officer field, as this will determine the Primary RO field in any register object. This field type should NOT be duplicated in the same register object. Use the 'Staff Dropdown' field type to configure the Secondary Responsible Officer field.


Workflow Configuration Settings

This settings page will let you configure the various workflows to be used within the system for each register type. Once given a name and description to the workflow, save and select to add objects to the workflow. You may further define each object’s properties and connect them to other objects, by dragging its connectors to the next object in the workflow.


To add a new workflow:

  • STEP 1: Click the 'New' button.
  • STEP 2: Enter a workflow name and description and click save. Workflow configuration sections will load at the bottom of the page.
  • STEP 3: To add an object to the workflow, select the object from object type list and click 'Add Object'. This will display the respective object in the workflow builder at the bottom of the page.
  • STEP 4: Once all the objects are added click on an object within the workflow builder and drag the linking line that appears to the object that it should link to.
  • STEP 5: To remove an object, click on the object and click 'Remove Object' button.

Note: Decision point-based workflow configurations can be done via the properties option available where all fields configured to be decision points for the object will be listed and the workflow which needs to be followed by the end users can be defined.

To set decision point-based workflow configurations:

  • STEP 1: Click the 'object' box which you wish to configure.
  • STEP 2: Click on the 'Properties' button.
  • STEP 3: Set the properties in the Workflow Element Details popup window and click the 'Save' button.


Compliance Type Settings

This settings page will let you define various compliance types in each compliance register type and link them to the created workflows of your organisation. This will then determine the workflow of a created compliance record. This is an important element in the overall structure of the system, as this type will be a mandatory selection when creating a new record. This could be done for all Register Types which can be selected via the ‘Register Type’ dropdown at the top of the page.

To add a new Compliance Type follow the steps below:

  • STEP 1: Navigate to Framework > Compliance Settings > Compliance Type.
  • STEP 2: Click on the 'New' button.
  • STEP 3:  Enter a name and a description for your Compliance Type.
  • STEP 4: Select a workflow from the workflow list. One workflow can be linked to multiple compliance types.
    After this is set up, when you click on a type of compliance you want to create from the sub menus in the ‘Add New’ button, you will be directly navigated in to the particular compliance type.

  • STEP 5: Click on the 'Save' button to save details.

Setting Compliance Code/Title in Header Section

By default the Compliance Code and Title will be displayed at the top of a Compliance Record. However, if you wish to change the order to Compliance Title - Incident Code, or display only the Compliance Code, or only the Compliance Name, this can be done in this Settings page.

To change code/title display at the top of a compliance record:

  • STEP 1: In the Compliance Type Settings page, in the dropdown field 'Record details page title' select the from the values 'Compliance Code' or 'Compliance Title'. Whichever that is to be display first.
  • STEP 2: Key in any separator (e.g. -, –, |, /, space) in the text box where the snippet is added and then select another field (Code or Title) from the dropdown.
  • STEP 3: Save details.
    The added snippet content will display in the header section of the Compliance Record. Below displayed is a default setup, where the [Compliance Code] -  [Compliance Title] is displayed in the header section.


Category Settings

This settings page will let you define categories and sub categories for created compliance types. Select the register type, compliance type, and click the 'Add New' button to create a category. Click 'Add New' under a category to create a sub category. Click the 'edit' icon next to a category or sub category to add further details such as help text, priority, and severity to it.

  • Filter categories by a particular Register Type, by selecting the 'Register Type' from the dropdown at the top.
  • To expand the list of categories and sub categories, click on the 'Expand All' button and to collapse the list, click on the 'Collapse All' button at the top-right corner of the page.

To add a new category:

  • STEP 1: Select a compliance register type from the dropdown. If the category falls into a compliance type, select the 'Compliance Type' from the dropdown, if it is a general category do not select a 'Compliance Type' from the dropdown.
  • STEP 2: Click on the 'Add New' button.
  • STEP 3: Enter a category name and click the 'save' icon next to it.
    Note: The category name is limited to 100 characters.

To add a sub category to a category:

  • STEP 1: Click on the + button to expand the category you wish to add the sub category to.
  • STEP 2: Click on the 'Add New' button. 
  • STEP 3: Enter a sub category name and click the 'save' icon next to it.

To enter more details for a category or sub category:

  • STEP 1: Click on the 'edit' icon placed at the end of the category/sub category name.
  • STEP 2: In the opened 'Category Details' page, enter 'Category Help Text' details to be displayed, select the 'Priority' from the dropdown, select the 'Severity' by clicking on the 'Select' button.
    Note: The category help text is limited to 4000 characters.
  • STEP 5: Click the 'Save' button at the top-right corner of the page to save details.

To edit the name or delete a category/sub category:

  • STEP 1: Click on the category/sub category name.
  • STEP 2: Click on the 'save' icon to save name, or 'delete' icon to delete the category/sub category.

 

Notification Templates Settings

This settings page will let you setup and configure various notification templates for compliance register types, to be available when triggering notifications. Select the notification name, type, description, notification method, and subject and body (for email notifications). You can specify under which conditions these templates are to be used in the Notifications page of this Settings area.

To create a new notification template:

  • STEP 1: Select the Register via the ‘Register Type’ dropdown.
  • STEP 2: Click the 'New' button at the top-right corner of the page.
  • STEP 3: Enter relevant fields. The following fields will be available:


Field

Type

Description

Mandatory/Optional

Name

Text

Define a name for the template. Name should be unique.

Mandatory

Notification Type

Dropdown

A dropdown including types; Compliance, Review, Action, Custom. Selecting a type will determine the snippets and trigger criteria of the e-mail.

Mandatory

Description

Text

A textbox to include a brief description of the e-mail template.

Optional

Notification Method
Checkbox
Select the method of the notification to be sent.
Mandatory

Subject

Text

E-mail subject. This will be visible in the e-mail in the 'subject' field.

Mandatory

Email Body

Text

Text area to include the e-mail body. Few common formatting functionality will be included here such as bold, italic, underline, strike through text; align text to right, left, centre, justify, remove alignment; Font size, spell check and snippet

Mandatory

  • STEP 4: Click 'Save'.

E-mail snippets are available to be included in the e-mail body. The snippets are categorised by the e-mail type, therefore, only the snippets that belong to the type selected will be visible in the list.

Snippets could be added via the ‘Variable’ dropdown in the header row of the Email body.

All snippets are described below.

Snippet

Email Type

Description

Compliance Code
  • Compliance
  • Review
  • Action

Code of the relevant Compliance

Compliance Title
  • Compliance
  • Review
  • Action

Title of the relevant Compliance

Compliance Responsible Person
  • Compliance
  • Review
  • Action

Name of the staff selected as compliance responsible person

Compliance Type
  • Compliance
  • Review
  • Action

Type that the relevant compliance belongs to

Compliance Categories
  • Compliance
  • Review
  • Action

Category that the relevant compliance belongs to

Compliance Status
  • Compliance
  • Review
  • Action

Current Status of the Compliance

Compliance Reported Date
  • Compliance
  • Review
  • Action

Date on which the Compliance requirement was reported

Compliance Description
  • Compliance

Detailed elaboration of the relevant Compliance

Compliance Reported By
  • Compliance
  • Review
  • Action

Name of the staff selected as the reporter

Compliance Requirement List
  • Compliance

A list of Compliance requirements

Last Reviewed By
  • Review

Name of the staff selected as ‘Reviewed by’ individual

Last Reviewed Date
  • Review

The last date on which the Compliance was reviewed

Next Review Date
  • Review

The next date on which the Compliance will be reviewed

Review Comment
  • Review

Comments on Review

Compliance Review List
  • Review

List of Compliance reviews

Action Title
  • Action

Title of the relevant action

Action Responsible Officer
  • Action

Name of the staff selected as action responsible officer

Action Start Date
  • Action

Start date of the Action

Action Actual Completion Date
  • Action

Actual completion date of the Action

Action Description
  •  Action

Detailed elaboration of the relevant Action

Compliance Action List
  •  Action

List of Compliance Actions

Reporting Officer of Compliance Responsible Person
  • Compliance 

Reporting officer of the staff selected as compliance responsible officer

Reporting Officer of Compliance Action Responsible Person
  • Action

Reporting officer of the staff selected as action responsible officer

 

Notifications Settings

This settings page will let you configure notifications to be sent out for compliance register types, upon various trigger criteria, according to a selected notification template, to various recipients, users, user roles or additional recipients. Notifications can be based on a trigger type if required. Further, create custom notifications for compliance objects, with custom trigger criteria, using custom trigger criteria configuration equations.

To create a new notification:

  • STEP 1: Click the 'New' button at the top-right corner of the page.
  • STEP 2: Enter relevant details. The following fields will be available:

Field

Type

Description

Mandatory/ Optional

Notification Name

Text

Define a name for the notification. Name should be unique.

Mandatory

Notification Type

Dropdown

A dropdown including types: Compliance, Review, Action, Entity Alert, Custom.

Note: Based on the selected notification type, the Trigger Criteria, Notification Template, and Notification Recipient options will vary.

Mandatory

Type
Dropdown
This dropdown will be displayed only for the Custom notification type.
Mandatory
Object
Dropdown
This dropdown will be displayed only for the Custom notification type. And based on the selected custom type, the object list will vary.
Mandatory

Trigger Criteria

Dropdown

List of all trigger criteria available for the selected email type. Refer below for more information.

Mandatory

Notification Template

Dropdown

Lists all notification templates created via Compliance Settings > Notification Templates filtered by the e-mail type.

Mandatory

Notification Recipient/s

Dropdown

Allow selecting recipients via their role within the compliance. Recipient list will differ according to type selected. Options available will be:

  • Compliance – Compliance creator, Compliance responsible officer, Reporting officer of compliance responsible officer
  • Review – Compliance creator, Compliance responsible officer, Reporting officer of compliance responsible officer
  • Action –  Compliance creator, Compliance responsible officer, Action responsible officer, Reporting officer of compliance responsible officer, Reporting officer of action responsible officer
  • Entity Alert Entity creator, Entity responsible officer, Reporting officer of entity responsible officer
  • Custom –  Compliance creator, Compliance responsible officer

Optional

User/s

Dropdown

 

Multi select dropdown of staff. This will allow to select a set of users to receive notifications upon selected trigger.

Note: If the user does not have permission to view the object, they will not be able to view the object, but will get a notification.

Optional

User role/s

Dropdown

Dropdown of all user roles created via Compliance Settings > User Roles. Selecting a user role will send a notification to all users who are assigned to the user role.

Optional

Additional Recipient/s
Text
Enter recipients to receive this notification in addition to the users and user roles above. Enter individual recipients in the manner shown below separated by a comma.
  • To notify a user who is selected against a field in an object {{<Object Name>.<Field Name>}} notation should be used.
  • To notify an external party need the external email ID/s and Phone number/s (E.g.: +XXXXXXXXXX) should be entered.
Optional
Active
Checkbox
Tick this checkbox to mark this notification as active, and deselect to mark it as inactive. 
Mandatory
Trigger Type
Dropdown
Select when the trigger will be executed from the following options:
  • On save selecting this option will execute the trigger when the user makes a change and clicks the 'Save' button.
  • On auto save  selecting this option will execute the trigger when the 'Auto Save' setting (under Miscellaneous Settings) is turned ON. When the auto save cycle runs in the background, if there has been any new changes in an incident record which requires an email to trigger, it will execute.
  • Open  selecting this option will execute the trigger for API based notifications; where an API based dropdown can be configured using API notifications. The system will send an API request when the dropdown is set to 'Open' and then receive an API notification with the data values to populate the dropdown. This has nothing to do with email or SMS notifications.
Mandatory


Trigger Criteria

The following trigger criteria will be available for each notification type.

Compliance

  • New Compliance created – When a new compliance is created a notification is triggered.
  • Compliance Requirement Assigned to a User – When a Compliance requirement is assigned to a user as a responsible person a notification is triggered.
  • According to Compliance Priority Notification triggered according to the compliance priority. Priorities to trigger this notification can be specified.
  • According to Compliance Severity – Notification triggered according to the compliance severity. Severities to trigger this notification can be specified.
  • According to Compliance Type – Notification triggered according to the compliance type. Types to trigger this notification can be specified.
  • Compliance Requirement Deleted – When a Compliance requirement is deleted a notification is triggered.
  • Custom Trigger Criteria – Refer Custom Trigger Criteria Configuration title below for more details.
  • Alert Submitted – Notification triggered when a compliance is submitted.

  Review

  • According To Compliance Review Frequency – Notification triggered on the review due date. If you select this trigger, you may select if consolidated emails are required or not by ticking the 'Send Consolidated Emails' checkbox, and add details to continue this trigger for a specified number or times by selecting from the 'Continue to remind every' section, on a recurring (daily, weekly, monthly, quarterly, yearly) basis, for a specified number of days before/after the review due date.

  Action

  • Action Created – When an action is created and saved a notification is triggered.
  • Action Due Date – When an action due date is created and saved, a notification is triggered.
  • Action Status Changed – When an action status is changed and saved, a notification is triggered.
  • Action Assigned to User – When an action is assigned to a staff.
  • According to Action Status –  When an action is in a selected 'Action Status' (in progress, completed, deferred, ongoing), a notification is triggered.
  • Action Review Date –  When an action is due/overdue, review notifications will be triggered, based on the new 'next review date'. (See section Periodic Reviews for Compliance Actions under Action in aritcle Compliance Management.)

  Entity Alert

  • Alert Submitted – Notification triggered when an entity alert is submitted.

Custom

  • Administrators will be able to define any custom notification rule based on the compliance type and the object. The only available trigger criteria will be ‘Custom’ where the trigger criteria can be defined using any single/multi select dropdown list value from the ‘Custom Trigger Criteria configurations’ area.
  • Custom trigger criteria – Refer Custom Trigger Criteria Configuration title below for more details.

Custom Trigger Criteria Configuration

A custom trigger criteria can be set for notifications to be triggered using this 'Trigger Criteria Type' for the following Notification Types: incident, investigation, resolution, close, risk, and submission. Custom trigger criteria for all these notification types will be set in the same manner.

The following configurations will be available to be set using the above custom trigger criteria builder.

Field

Description

Select field
Select the object from the dropdown to which you wish to set the custom trigger for. Expand the object by clicking on the + icon to list all its fields under each object. Once you select the field, it will add it on to the criteria builder area.
Example:
In the screenshot, in line 1, the object > Case Details + the field > Investigation Status has been selected in the first line.
You may then use the operators as explained below, and build the function you wish, to create your customised trigger.
Values
If the above selected field has several values assigned to it (e.g. in a dropdown), this will list under the values dropdown. These values can be used with the EQUAL or NOT EQUAL operators to use in your customised function.
Example:
In the screenshot, in line 1, the object > Case Details + the field > Investigation Status has been selected and the EQUAL operator has been selected, and the Value dropdown has been selected as 'Not Started'.
Operators
AND – Use this operator to denote that whatever follows this, will have to be fulfilled too, in order to trigger the notification.
OR – Use this operator to denote that whatever criteria mentioned before this or after this requires to be fulfilled, in order to trigger the notification.
EQUAL – Use this operator to add an = sign to trigger a notification if it equates the field to a selected value.
NOT EQUAL – Use this operator to add a != sign to trigger a notification if it does not equate the field to a selected value.
( ) – Use these bracket operators to group several functions when using multiple trigger criteria.
CHANGE – Use this operator when you want to trigger a notification whenever a field is changed to any value (unlike in EQUAL and NOT EQUAL, where it will trigger only when equal/not equal to a specified value). The 'Change' syntax should be written as follows: 
{CHANGE.objectname.fieldname} for this to function correctly.
  • STEP 3: Click on the 'Save' button at the top-right corner of the window to save your settings.
    Note: An email notification will be triggered irrespective of the compliance status, once saved.


Miscellaneous Settings

This settings page will let you configure various settings within the Compliance module. Note that changes done here will impact the overall module (all Compliance Register Types).

Below listed are settings that are applicable to the Compliance system.

Field
Description

Records per Page in Compliance Register

Defines the number of records displayed in the compliance registers by default. This will commonly apply to all registers available within the compliance module.

Display Longitude and Latitude in Incident Details
Enables to show the Longitude and Latitude in Compliance Details underneath the Location field.

Automatically select Responsible Officer from

Enables to automatically select the Responsible Officer from the Directorate or Business Unit selected for the compliance.

Display detailed warning message on submission

Enables to show a detailed warning message (validation message) upon submission of records. Disable all objects when Compliance is closed.
Default Compliance Status selected in Register
Enables to select a Compliance status via the dropdown which appears. The selected status will be the default status.
Set default Sign Off authority for Compliance

Enables to set up the default signoff authority based on User Role or User.

Hide Add New button in Register
Enables hiding the ‘Add New’ button is the Registers.
Time for Bulk Emails in Compliance (this will consider the server time)
Define the time at which the bulk emails in compliance should be triggered.
Authenticate when navigating via notification hyperlinks
Authenticate users when navigating via the notification hyperlinks.

Activate all active email triggers in Incident and compliance

Activate/deactivate all active email triggers in both Incident and Compliance modules.
Disable hyperlinks in email snippets for all incident and compliance notifications
Disable by selecting this, to send hyperlinks in email snippets in the email body in both Incident and Compliance modules.
Default Sort Order in Compliance Register
Select the sort order in compliance registers from a dropdown, to be from compliance code or compliance title, in ascending or descending order.
Enable Synchronisation of Compliance Action Progress 
Enable synchronising action progresses by selecting this checkbox.
Auto Save Frequency (in Minutes, keep blank to turn off)
Enter a number in this field to denote the amount of minutes to auto save incident pages at a pre-defined frequency to prevent data loss. This will help users if in case of accidental closing the browser window or unexpected page crashes.
  • The mandatory validations will not be validated at the time of auto-save.
  • The user will not be able to do a manual save at the time the auto-save is happening, but could do so at any other given time. 
  • At the time of an incident creation, if the auto-save happens the incident will get saved as a ‘Draft’ and will appear in the register as a ‘Draft’ for the incident creator only.
Notes:
  • The minimum auto-save frequency is 5 minutes. Leaving it blank would turn off the auto save feature.
  • Decimals, alphabets, and characters cannot be entered here.
  • The incident will be created and saved as a ‘Draft’ irrespective of the miscellaneous setting ‘Disable draft functionality in Incident Details’ being ticked. At the time of an incident action creation, the action will get saved as a ‘Draft’ and will appear in the action register for the action creator only.
  • The incident will be created and saved as a ‘Draft’ irrespective of the ‘Enable Approval’ setting being ticked. The auto-save will run and save information only if the user has done any changes to the record between the frequency cycles. The auto-saved information will be updated in incident history.
  • The auto save functionality will not work for the following objects: Linkage object, Document object, My Quick Update, Incident Portal.


Click on the 'Save' button to save changes made to any of the settings.

Note: Only applicable settings to Camms.Risk Compliance are listed here.