Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Creating a custom hierarchy

Updated on May 25, 2021

Pega Know Your Customer uses by default PegaKYC-Data-Type- as the base class where all the KYC Types of the application reside. If you decide to create your own class structure, its root must inherit either by direct or pattern from this class. That way, all the engine assets located under that base class will be accessible, and your KYC Types will be fully functional.

Once you have created your root class, along with the subclasses that might be required, it is time to register it so that the KYC Rule Manager Studio can use it to render the appropriate navigation tree. The registration is done by using the Dynamic System Setting KYCTypeRootClass that is associated to the KYC ruleset. For example, if you created your class structure under MyCo-Data-Type-Policies-, you should configure the Dynamic System Setting as in the following image:

After these changes are done, the hierarchy displayed at the KYC Rule Manager Studio will be the one defined by your class structure.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us