As explained in Accessing external data providers, the application uses subcases to manage the results obtained through the eScreening services for a given customer. The subcases can be configured to change their behavior based on your needs slightly.
Server connection attempts
You can configure the number of times that the application tries to connect to the eScreening server. If the number of attempts to connect to the server exceeds the limit, the screening case is automatically resolved. Set the following Dynamic System Setting with the desired amount of attempts: PegaFS eScreeningAttemptsLimit=<number of attempts>.
Data validity period
You can configure the amount of time that the eScreening data stored at the Master Profile for a given customer is valid. At the point of the process where the application determines if the customer goes through e-Screening, the system checks if the data is already available for that customer on the Master Profile and, if there is, it checks its validity time. If the data is still valid, the system bypasses the creation of the case and reuses the existing data. If the validity time is exceeded, the system creates a new case and invokes the eScreening business service to get fresh results. The following Dynamic System Setting can be used to establish that validity period: PegaFS ScreeningValidity=<validity period in days>.
Pega Client Lifecycle Management and KYC comes with a default data propagation logic to move the results of the eScreening cases to the main journey case. That way, the data becomes available to any subsequent logic that might require it, for example, customer risk. If you want to add more data to the one that is currently propagated by the out of the box, you can modify an extension point created for that very purpose, see the SynchronizeScreeningData_Extension. data transform.