The locators have two key attributes: Purpose and Key. The Purpose is presented as the category, and the Key is analogous to the subcategories. The following table includes some examples of locators that are used in Pega Client Lifecycle Management and KYC.

When the application creates a due diligence case, it initializes the locators that determine the KYC Types managed by that case (DDPurpose and DDKey properties). These locators are compared against those provided in the KYC Applicability Matrix to display the appropriate KYC questionnaires to the case.

The data transform GetKYCTypeLocators programmatically populate the initialization of the locators at the case. In Pega Client Lifecycle Management and KYC, each case type has a copy of this data transform, which uses the due diligence orchestration mode configuration to set the right locators. For example, for a customer onboarded in Australia with products in the United States and Spain, the values for the locators set on the cases under each of the case orchestration modes are shown in the following tables.

In the intermediate mode, a single Global KYC/AML case is created to address all the global, regional and local regulations. Thus, while setting the DDPurpose and DDKey on the case, all the keys that apply to the customer under the AML category are set in the Global KYC/AML case itself, thereby driving the applicability of the corresponding KYC Types. The same is for the simplified mode where all the relevant purposes and keys are populated on the single Global KYC/AML case that is created to cover all the due diligence categories and subcategories.

You can update the applicability of the KYC types provided with Pega Know Your Customer Regulatory Compliance or configure the applicability of your custom KYC types by copying and updating the KYCApplicabilityMatrix decision table and the GetKYCTypeLocators data transform in your implementation layer classes. Or you can also configure even Standard Filtering applicability. However, use the KYC Applicability Matrix to configure the applicability without overriding the KYC Types, unlike the Standard Filtering applicability.