Good practice for Pega Customer Service custom Customer class
In Pega Marketing for Financial Services, we usually extend the base customer class (PegaMarketingFS-Data-Customer) to support the loading of customer data.
In Pega Customer Service (CS), I see we have the Contact class (PegaCA-Interface-Contact) which has directed inheritance with PegaData-Contact.
If we want to have a custom Customer (or call it Vendor, Merchant, etc.) class. It is ok to extend PegaCA-Interface-Contact class?
Pegasystems Inc.
US
For Customer Service for financial services the customer class OOTB is PegaCPMFS-Data-Customer-Ind ( for individual ) or PegaCPMFS-Data-Customer-Org ( for organizations ) both of these classes can be extended with an implementation class that has directed inheritance to these classes.
Customer service for financial services also leverages the horizontal Customer Service Contact class that represents the customer in certain places being PegaCA-Interface-Contact which can also be extended as an implementation class with directed inheritance.