Should we utilize Direct- or Pattern-inheritance of Pega Strategic Application (Framework) classes?
Utilize Direct-inheritance as this promotes a Pattern-inheritance path in your Enterprise Class Structure, allowing you to implement Application-specific behavior (from MyOrg-MyCustomerServiceApp-Data) and Enterprise-specific behavior (from MyOrg-Data) that further specializes the behavior you inherit from Pega classes.
Discussion on this topic was sought from theLSA Data Excellence (Pega 8.4) webinarconducted in July 2020. The webinar and its full set of discussions that arose from it are available atLSA Data Excellence: Webinar, Questions & Answers.
Use direct inheritance for Pega Strategic Application (Framework) classes. This approach ensures your application classes follow a clear pattern-inheritance path across the enterprise class structure. It allows application-specific behavior to be defined in your app layer while still inheriting enterprise-level behavior from shared data classes. This creates better reuse of rules across different applications within the organization. It also supports consistent specialization from Pega base classes without breaking the inheritance hierarchy. Overall, direct inheritance keeps the class structure clean, scalable, and aligned with enterprise design principles.