Overview
This document ensures all required configurations and validations for Adverse Media Search Integration are completed and verified through a Maker-Checker approach.
Each item must be marked TRUE once completed by the Maker and validated by the Checker.
Legend
|
Term |
Role Description |
|
Maker |
Responsible for executing the setup/configuration |
|
Checker |
Responsible for reviewing and validating the setup |
Implementation Details
|
Client / Organization |
|
|
Implementation Date |
|
|
Document Version |
v1.0 |
|
Document Owner |
|
Configuration Checklist
|
# |
Checklist Item |
Maker |
Checker |
|
1.1 |
Configured Remote Site Settings |
|
|
|
1.2 |
Configure Custom Field Mappings for CLEAR Integration in Custom Metadata (Clear Mapping ) |
|
|
|
1.3 |
Thomson Reuter API (Credentials and Endpoint) |
|
|
|
1.4 |
Feature Entitlement (Features that we need to enable) |
|
|
|
1.5 |
CLEAR Buttons are Created on the Source Object. |
|
|
|
1.6 |
Assign Thomson Reuter CLEAR Permission Set to User |
|
|
|
1.7 |
Lookup Field for Source Object on TR
|
|
|
|
1.8 |
Related List is present on Source Object |
|
|
Instructions
-
Use this checklist during the implementation and deployment of the Payment Connect app.
-
Check items off only once they are configured (Maker) and reviewed (Checker).
-
Log any exceptions, deviations, or follow-up items in the Notes column.
-
This checklist should be version-controlled and retained within the implementation workspace for audit purposes.