After the KYC Types are created, they need to be configured in the application in accordance with the relevant business scenarios. The configuration must take into account the different points in the process where the KYC Types is used, as well as the business logic that drives the applicability of each specific KYC Type at each of those points.

For example, an onboarding application consisting of multiple stages might only require the dynamic nature and audit capabilities of the KYC Types in one of those stages. You must configure that stage, with its associated cases and processes, in order to present the applicable KYC Types to the users. Depending on particular business and operational needs, each application can have multiple points where KYC Types are used.

At the same time, the application needs to determine which KYC Types are relevant at each of these points of the process. For example, a KYC Type created to capture the information from customers of type individual during an onboarding process is not relevant if the customer that is being onboarded is an organization. In addition, the KYC Type might be relevant in a business-specific scenario but, according to the operational model of the financial institution, this KYC Type must not appear at certain points in the process.

The following two sections explain how to configure these two important aspects of the KYC Types: the points of the application where they are used, and the business logic that drives their applicability.

• Configuring case processes
• Defining applicability conditions

• Pega Know Your Customer Engine