Class hierarchy structure
An enterprise can have a complex organizational structure with many locations. For example, an electronics retailer sells mobile devices and laptops in stores, online, and social media. The electronics retailer needs a way to manage their channels, products, and customers. The customers of the electronics retailer are in different countries. The electronics retailer must maintain compliance with the regulations of each jurisdiction.
With some application development platforms, it may be best to create separate copies of the application for each product, region, or channel. Or, you may need to manage the complexity of the different channels and regions in a single application. The result is hard-to-manage enterprise applications that do not scale.
Pega Platform™ enables you to organize your application by using the same dimensions as your business. Pega Platform makes reusing common policies and procedures easy while allowing for differences between products, regions, channels, and customer segments.
The application is structured by designing the right applications, objects, and Cases using App Studio. When designed effectively, the system automatically generates an appropriate class structure. The goal isn't to create a class structure itself, it emerges as a result of good design. Typically, a Lead System Architect (LSA) is responsible for designing the overall system architecture.
Match the numbers to the following image to learn more about layers in the class hierarchy structure:
1. Implementation Layer: The Implementation Layer contains one or more applications customized for a specific division or line of business. For example, a clothing retailer consists of two brands of stores. Each brand can create its own Implementation Layer for brand-specific assets, such as styling and policies.
2. Unit Layer: If you enable the Division Layer, you can optionally enable the Unit Layer, which contains assets that are used on a unit-wide basis.
3. Division Layer: The Division Layer is optional and contains assets used on a division-wide basis. Assets in the Division Layer may apply to a line of business, region, or brand. For example, you save a Service-Level Agreement (SLA) Rule that defines the expected response time to a customer complaint in the Division Layer to enable all applications within that division to use that SLA Rule.
4. Organization Layer: The Organization Layer contains the assets that are used on an enterprise-wide basis. For example, access to an external customer database is an integration point that you can add to the Organization Layer.
5. Pega Platform Layer: The Pega Platform Layer contains the built-in assets that are necessary for processing Cases and other work in Pega Platform applications. This Layer also includes the assets that Pega Platform uses.
Note: You can bundle organization, division, or unit assets into applications for ease of packaging.
Constellation architecture
Constellation architecture supports a scalable design that enables the reuse of assets across the organization. By defining a Data Model first, it helps identify opportunities for data reuse across multiple processes, which is essential for building a consistent and efficient application framework. This approach allows for more effective asset management and ensures that the architecture is designed to maximize business value and streamline application development.
Constellation architecture represents a shift from customization to configuration. With Constellation, you configure your application’s Data Model, which generates a largely prescriptive overall experience. From the Data Model, Constellation generates the end-to-end experience, including the UI and actions. This means shorter development time, a more consistent user experience across channels, easier upgrades, and minimal maintenance.
Constellation offers pre-configured UI templates, as well as prescribed navigation, workflows, and information architecture, all of which enable our clients to take advantage of our 40 years of experience in building enterprise applications and more easily build consistent, error-proof applications in record time.
Note: For more information on structuring enterprise architecture for reuse, see Constellation and business architecture.
Match the numbers to the following image to learn more about the Constellation architecture:
1. Constellation design system: A library of pre-built UI components and patterns that is built on React.
2. Constellation architecture: New UI architecture and modeling experience that connects Constellation components and beyond to back-end APIs.
3. Constellation DX API: A set of model-driven API endpoints that power the out-of-the-box user experiences and custom front-end experiences.
4. Pega engine: Powers the business logic.
Note: For more information on the Constellation architecture, see Constellation UI.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?