Ansarada GRC: Creating Source Obligation

Ansarada GRC: Creating Source Obligation

Creating a Compliance Process from an Obligation

  1. Open an Obligation and click the Integration tab 1. Click the Create Compliance Process from Obligation button 2.

    'Creating a Compliance Process from Obligation'

  2. The New Compliance Process window displays. Enter values for all fields. Leave Convert Sub Obligations to Process Controls 2 unticked to create the Compliance Process only (See the next section for more information on when this is ticked.). Click the Save icon 13 to create the new Compliance Process. (See New Compliance Process window elements for details on each field in this window.)

    'New Compliance Process' window

    Note: If you do not have Compliance Risk configured, the Risk field 11 will not appear.

  3. The new Compliance Process displays. Click the Source Obligation tab.

    ''

  4. The Source Obligation tab displays the current information of the Obligation.

    ''

New Compliance Process window elements

ID

Element

Description

1

‘Information’ icon

Click this icon to display information on creating a Compliance Process.

2

‘Convert’ checkbox

Select this checkbox to be able to convert the Sub Obligations of this Obligation to Process Controls.

3

‘Process Number’ field

The Obligation number will default to the Process Number field, but this may be changed to another unique Compliance number.

4

‘Record Status’ field

Click this field and select the Record Status from the drop-down list.

5

‘Title’ field

The Obligation ‘Title’ will default to the Title field. This may be edited.

6

‘(Business Unit)’ field

Select a Business Unit responsible for the Compliance Process.

7

‘Category’ field

Select the relevant Compliance Category.

8

‘Responsible Officer’ field

select a Position from the drop-down list. This Position will be responsible for the Compliance Process. Select Edit access for this Position’s Security Group 12.

9

‘Tags’ field

Apply one or more Tags to the Compliance Process to associate the Record with other Records of similar application. See Tags in the Glossary for more information.

10

‘Description’ field

The Obligation ‘Directional’ will default to the Description field. This may be edited.

11

‘Risk’ field

The Obligation ‘Consequence’ will default to the Risk field. This may be edited.
Note: This is a configurable field and may not appear on your site.

12

‘Security’ access

Select the security access of the Security Groups. Ensure that the Responsible Office’s 8 Security Group has Edit access.

13

‘Save’ icon

Click the Save icon to create the new Compliance Process.

14

‘Cancel’ icon

Click the Cancel icon to close this window without processing.

    • Related Articles

    • Ansarada GRC: Creating a Process Controls from an Obligation or Sub-obligation

      Creating a Process Controls from an Obligation Open an Obligation and click the Integration tab 1. Click the Create a Process Control button 2. The New Task window appears. Select the Compliance Process this new Process Control is created in. The ...

    • Ansarada GRC: Obligation Maintenance

      Identifying Awaiting Updates Owners of the Compliance Process will receive a notification email informing them an update has arrived and is ready to be applied. Compliance Processes with awaiting updates will have their Source Obligation cells ...

    • Ansarada GRC: Adding a Source Obligation

      Obligations and Sub Obligations can be added to existing Compliance Process and Process Controls as their Source. Adding a Source Obligation from a Compliance Process Open the Compliance Process you want to add an Obligation Source to. Click the ...

    • Ansarada GRC: Turning off Obligation Tasks

      Are your users overwhelmed by the large volume of tasks being generated to review each new LexisNexis Obligation update? Our system provides the flexibility to turn off these tasks. By doing so, each Obligation (or Sub-Obligation) Owner and Notify ...

    • Ansarada GRC: Events Maintenance Section

      Every Module has a Maintenance Section where the configuration can be done. Only Administrators can access the Maintenance Configuration Events tab. Only Administrators and Administrators - Events can access the Events Maintenance menu items. Events ...