A class hierarchy has been created to organize and store instances of KYC Type rules. The class hierarchy is organized by global regions and regulations and it has a corresponding set of rulesets that follows the same structure. In addition to the class hierarchy shipped with the application, there are pre-configured due diligence rules that can serve as a design model or as reusable assets in production implementations.

The use of class structures to organize KYC Type rules is intended to facilitate configuration and maintenance updates while allowing clients to logically separate their due diligence rules. Specialized class hierarchies should be constructed to store the client's specialized due diligence rules. The client's specialized classes can be configured to inherit from the PegaKYC-Data-Type-Policies- classes to promote reuse.

• Creating the root data class
• Configuring the root class
• Creating a global policy class
• Viewing a sample class structure
• Creating KYC Type properties to store due diligence data
• Creating KYC Type rules
• Adding a new KYC Type from a workbook
• KYC Type data extension point configuration

• Pega Know Your Customer Engine