Configuring eScreening services
In order to comply with laws regarding know your customer (KYC), anti-money laundering, countering the financing of terrorism, and anti-bribery-corruption, banks may want to connect to a varity of eScreening services.
To enable and configure eScreening services, do the following tasks.
Enabling eScreening
To use eScreening services, you must first enable them.
In the Dev Studio header search text field, enter licensedToUseeScreening and select the dynamic system setting.
Change the value to true.
Configuring eScreening server connection attempts
You can configure the number of times the application tries to connect to the eScreening server. If the number of attempts to connect to the server exceed the limit, the screening case is automatically resolved.
In the Dev Studio header search text field, enter eScreeningAttemptsLimit and select the dynamic system setting.
Change the value to your desired amount of attempts.
Configuring the amount of time that the eScreening data is valid
You can configure the amount of time that eScreening data is valid. If the time period is exceeded, a new case is created to get fresh data from the screening server.
In the Dev Studio header search text field, enter ScreeningValidity and select the dynamic system setting.
Change the value to your desired amount of days.
Adding data to the eScreening case
If you want to propagate data from the screening case, in addition to the default data, to the main case so that it can be used during onboarding, due diligence, and so on, you must map this data in the appropriate data transform to include additional fields.
In the Dev Studio header search text field, enter SynchronizeScreeningData_Extension and select the data transform.
Modify the data sources and data fields as needed.
Previous topic Configuring World-Check integration Next topic Automatic detection of components