Free cookie consent management tool by TermsFeed

Modifying OFAC Integration

This content applies solely to Connected KYC, which must be purchased separately from the Appian base platform. This content was written for Appian 23.3 and may not reflect the interfaces or functionality of other Appian versions.

Introduction

Some modifications to the OFAC integration require more changes than what is provided in the System Administration Center. These changes include:

To learn about setting up and using the OFAC integration, see Manage OFAC Integration.

Changing the search parameters

If a fuzzy name match on the customer's name is not specific enough or you would like to include more attributes of the customer in the search, create a new integration.

See the Trade.gov website for the available consolidated screening search parameters.

To change the search:

  1. If you want to use customer information that isn't included in the default solution, add the fields to the associated customer data types (CDT) and database tables. See Modifying Record Fields for more information.
  2. Create a new integration using the AS FS Trade.gov Consolidated Screening connected system.
  3. Update the integration in the AS FS CS Integration process model.
  4. Update the integration in the rule!AS_FS_CS_UT_queryAndMapScreeningResults expression rule.
  5. If different results are returned or they are returned in a different style, update the AS__GRD_consolidatedScreeningCheckResultsGrid, AS__CPS_reviewConsolidatedScreeningCheckTask_Results, and AS__CPS_reviewConsolidatedScreeningCheckTask interfaces and the AS_FS_CS_UT_mapResultsSources expression rule.

Saving more information

Each time the integration is called, the following information is stored in the AS_FS_CS_RESULT table:

  • Record ID (from the application) of the that the search was performed for.
  • Recored Type Code: Used to distinguish the record that the search was performed for. This will be _ for .
  • Customer name used in search.
  • Customer ID (from the application).
  • Total number of results.
  • Sources checked.
  • Date and time of search.

If results are returned from the consolidated screening, stores the following information about each result in the AS_FS_CS_RESULT_FINDING table:

  • Result ID: key from the AS_FS_CS_RESULT table.
  • Score: how close of a match the result is.
  • Name: from the consolidated screening list.
  • Alt. Name(s): alternative names for the result.
  • Source: which list the information is from.
  • Source URL.
  • ID: from the consolidated screening list.
  • Is relevant: whether the result is marked as relevant.

More information from the API, such as addresses or citizenships, can be also be stored or displayed. The Trade.gov website provides a list of available fields and their data types.

To save more information, add new fields to the OFAC integration records. See Modifying Record Fields for more information.

The following may need to be updated when adding fields to these records:

  • Database tables: AS_FS_CS_RESULT and AS_FS_CS_RESULT_FINDING.
  • CDTs: AS_FS_CS_Result and AS_FS_CS_Result_finding
  • Data store: AS FS OFAC Data Store
  • Main interfaces: AS__CS_reviewConsolidatedScreeningCheckTask and AS__GRD_consolidatedScreeningCheckResultsGrid
  • Main expression rules: rule!AS_FS_CS_UT_queryAndMapScreeningResults and rule!AS_FS_CS_UT_mapResultsSources.

Changing the try count

will try five times to connect to OFAC before designating the integration call as a failure.

If your IT has an integration try threshold that is different than five, change the try count by updating the cons!AS_FS_CS_VAL_TRY_COUNT constant.

Feedback