Thomson Reuters Regulatory Intelligence Spoke
Thomson Reuters Regulatory Intelligence Integration (TRRI) helps you gather, monitor and analyze regulatory data and track developments in a complex regulatory environment. Use GRC: Thomson Reuters Regulatory Intelligence spoke to integrate with Thomson Reuters and consume the TRRI feeds into your ServiceNow instance.
Overview
- Receive regulatory feeds from Thomson Reuters that are relevant to your organization
- Transform and map the regulatory taxonomy from Thomson Reuters to your internal regulatory taxonomy
- Load the transformed data into your ServiceNow instance and manage regulatory changes
See the pre-setup checklist for the integration:
- Configure feed settings: Configure and setup the feed content, delivery settings, and delivery location (where the feeds are delivered to) in the Thomson Reuters Regulatory Intelligence (TRRI) feeds user interface.
- Set up MID Server: Thomson Reuters sends the regulatory feed files to the SFTP server configured on the Thomson Reuters portal. An administrator should set up a MID Server with SSH capabilities for the GRC: Thomson Reuters Regulatory Intelligence spoke to work and to ingest the feed file data from the SFTP server into the ServiceNow® instance. The MID Server runs as a Windows service or a UNIX daemon to facilitate communication between an instance and the external applications.
See the following section for information on the tasks included in the Thomson Reuters Regulatory Intelligence guided setup:
- Connections: Create and validate the connection that is required for an integration with Thomson Reuters. Tasks in this step include:
- Create Connection
- Validate Connection
- Submit OAuth Credentials
- Activate Integration Flows: Set up a schedule and activate the integration flows at
different times. It is recommended to run the flows with a time gap, for example, a gap of 12
hours between the flows. Tasks in this step include:
- Configure the flow that inserts feed files into feed registry
- Configure the flow that moves processed feeds into destination directory
- Create Internal Taxonomy: Create your internal taxonomy to categorize and classify the
regulatory content. Internal taxonomy can be a multi-hierarchical structure. You can manage
external regulatory content and map Thomson Reuters taxonomy to your internal
taxonomy. Tasks in this step include:
- Create Internal Taxonomy for Regulatory Bodies
- Create Internal Taxonomy for Content Types
- Create Internal Taxonomy for Jurisdiction
- Create Internal Taxonomy for Themes
- Create Internal Taxonomy for Sectors
- Map External Taxonomy to Internal Taxonomy: Map the source taxonomy from Thomson Reuters with the internal taxonomy that you have created. Task in this step include Map Taxonomy.
Request apps on the Store
Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Integration Hub subscription
This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.
Spoke requirements
Thomson Reuters deposits the regulatory feed files at the SFTP location configured in their portal. Create a new SFTP connection and import the feed files imported into your ServiceNow instance. The spoke requirements are:
- Create a new SFTP connection by entering the following details:
- Add custom name, host IP address, port number, username, and password to connect to the SFTP server
- Source path to the directory that contains the feed files. See the sample source path:
- Windows users: C:\Users\samadmin
- Non-Windows users: /Users/custom.name/samadmin
- Destination path to the directory where the successfully imported files should be moved.
See the sample destination path:
- Windows users: C:\Users\samadmin\processed
- Non-Windows user: /Users/custom.name/samadmin/processed
- Validate the connection before it can be used in the integration flows.
- Submit OAuth credentials to provide the documents related to the regulatory event type of feeds.
Spoke dependencies
- GRC: Regulatory Change Management
- ServiceNow Integration Hub Action Template - Data Stream
- ServiceNow Integration Hub Action Step - SFTP
- GRC: Policy and Compliance Management
- GRC: Advanced Risk
Spoke actions
The regulatory data received from Thomson Reuters is processed and it is brought into the staging tables in a ServiceNow® instance.
- Get the related source documents for the regulatory events
- Get the Thomson Reuters feed file names from the SFTP source path
- Move the Thomson Reuters processed files to the destination path
- Trigger the Thomson Reuters scheduled import job after getting the file names from the SFTP server
- Validate the Thomson Reuters path and credentials for the Thomson Reuters SFTP connection
Available actions include:
| Category | Action | Description |
|---|---|---|
| Get the related documents | Get the related documents for the regulatory events | Get the related source documents for the regulatory events |
| Get the feed file names | Get the Thomson Reuters feed file names | Get the Thomson Reuters feed file names from the SFTP source path |
| Move the processed files to the destination directory | Move the Thomson Reuters processed files | Move the Thomson Reuters processed files to the destination path |
| Trigger the scheduled import job | Trigger the Thomson Reuters scheduled import job | Trigger the Thomson Reuters scheduled import job after getting the file names from the SFTP server |
| Validate the path and the credentials | Validate the Thomson Reuters path and the credentials | Validate the Thomson Reuters path and credentials to test the path and the credentials for the Thomson Reuters SFTP connection |
Spoke module
| Module | Description |
|---|---|
| Thomson Reuters Guided Setup | Provides step-by-step instructions to configure the setup with GRC: Thomson Reuters Regulatory Intelligence spoke |
| Connection & Credential Aliases | Set up the SFTP and OAuth connection and credentials |
| Connections | File connection information record from Thomson Reuters. Click
Validate to validate the connection. In case you encounter any
issues in validating the connection, triage it using an integration log. If you do not want to use a connection, you can move it to draft state by clicking Move to draft. In integration, only the File Connection Information record for which the state is Validated is used in the flows. |
| OAuth Registry Entry | Displays the record when OAuth connection and credential are created via the shipped connection and credential alias |
| OAuth Credentials | Displays the record when OAuth credentials are created |
| Feed Registry | Contains a record for each of the feed files located in the source directory of the SFTP location |
| Integration Logs | Displays integration logs. Contains integration errors, for example, errors observed while validating a connection or other errors in the integration flows |
| Data source | Data source that ingests the feed files from the SFTP location and creates a record automatically in the regulatory feed table |
| Scheduled Import | The job that scans and searches for an oldest entry in the feed registry |
| Taxonomy XML Configuration | Record being shipped as part of Thomson Reuters component. Contains XPaths and attributes that are needed to parse the uploaded Thomson Reuters taxonomy file in XML format |
| TR | Regulatory Bodies | Configure a new record for the external regulatory body for Thomson Reuters |
| TR | Content Types | Configure a new record for the external content types for Thomson Reuters |
| TR | Jurisdictions | Configure a new record for the external jurisdictions for Thomson Reuters |
| TR | Themes | Configure a new record for the external themes for Thomson Reuters |
| TR | Sectors | Configure a new record for the external sectors for Thomson Reuters |
| Taxonomy Mapper | Map Thomson Reuters taxonomy to internal taxonomy |
| Tables | Fields |
|---|---|
| sn_grc_reg_change_external_theme | External Regulatory theme |
| sn_grc_reg_change_external_regulatory_body | External Regulatory body |
| sn_grc_reg_change_external_sector | External Regulatory sector |
| sn_grc_reg_change_external_content_type | External Regulatory content type |
| sn_grc_reg_change_external_jurisdiction | External Regulatory jurisdiction |
| sn_grc_reg_change_ theme | Regulatory theme |
| sn_grc_reg_change_ regulatory_body | Regulatory body |
| sn_grc_reg_change_sector | Regulatory sector |
| sn_grc_reg_change_ content_type | Regulatory content type |
| sn_grc_reg_change_ jurisdiction | Regulatory jurisdiction |
Spoke user roles
The GRC: Thomson Reuters Regulatory Intelligence spoke uses the RCM IT Admin (sn_grc_reg_change.it_admin) role provided by the Regulatory Change Management application to control access to the data.
The RCM User assesses the applicability of a regulatory feed record, initiates impact assessments, and completes the assigned regulatory change tasks and action tasks.
The RCM user creates the regulatory change tasks and the action tasks. The RCM Manager assigns the regulatory feeds and regulatory change tasks and approves them.
Connection and credential alias requirements
Integration Hub uses aliases to manage connection and credential information. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection. For more information, see Connections and Credentials.
For information about setting up the spoke, see Create a connection record for the GRC: Thomson Reuters Regulatory Intelligence spoke.
MID Server requirements
MID Server runs as a Windows service or a UNIX daemon to facilitate communication between an instance and the external applications. Thomson Reuters sends the regulatory feed files to the SFTP server configured on their portal. A MID Server with SSH capabilities should be set up by an administrator for GRC: Thomson Reuters Regulatory Intelligence spoke to work and to ingest feed file data from the SFTP location into the ServiceNow® instance.