Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 5
Enterprise Class Structure
Pega Platform makes reusing common policies and procedures easy while allowing for differences between products, regions, channels, and customer segments. Pega Platform facilita la reutilización de políticas y procedimientos comunes al tiempo que permite diferencias entre productos, regiones, canales y segmentos de clientes. Pega Platform supports this capability by using a class hierarchy structure called Enterprise Class Structure (ECS). You can share any rule placed in an ECS layer across multiple applications. You can adjust existing ECS layers as business operations change. ECS also enforces best practices around reuse and standardization as the system expands to other lines of business.
Enterprise Class Structure layers
Pega Platform layer The Pega Platform layer contains the built-in assets necessary for processing cases and other work in Pega applications. This layer also contains the assets Pega Platform uses. La capa de la plataforma Pega contiene los activos integrados necesarios para procesar casos y otros trabajos en las aplicaciones Pega. Esta capa también contiene los activos que usa Pega Platform.
Organization layer The Organization layer contains the assets used on an enterprise-wide basis. Such assets are rules for enterprise-wide business logic such as standard properties, decision tables, and service level rules. For example, an online retailer reuses a property that holds a customer account number throughout the retailer's business. The applications used across the enterprise can rely on the same account number property without having to make copies of the property in every application. The Organization layer also contains enterprise-wide data assets such as classes and rules for data stored in the system, and classes and rules for access to data in external systems, via connectors. For example, access to an external customer database is an integration point that may be added to the Organization layer.
Division layer The Division layer contains the assets used on a division-wide basis. The division layer is the middle level of the three-level organization hierarchy (Org-Div-Unit) and is available for use in every application. Assets in the Division layer may apply to a line of business, region, or brand. For example, a line of business wants to reuse a service level rule that defines the expected response time to a customer complaint in all of its applications. Placing the service level rule in the Division layer provides all applications within the division with access to the service level rule through pattern inheritance. This reuse avoids the need to create and maintain separate copies of the service level. Note: The Division layer is an optional layer. In larger organizations, the Division layer can help to manage the reuse of rules and other application assets.
Framework and implementation layers
The Framework layer contains assets that can be extended in specific implementations. The framework layer may be comprised of one or more generalized applications, such as a standard Pega application for a specific industry, or an extendable custom application. The Implementation layer defines an application customized for a specific division or line of business. An implementation layer application may extend one or more framework layer applications. For example, a clothing retailer consists of two brands of stores. One brand focuses on the upscale clothing market, while the other brand runs a value-oriented chain of stores. Each brand needs to manage item returns. The retailer can develop a generalized application that manages clothing returns in the framework layer. Each brand can then create its own implementation layer to customize the returns process. Each customized application contains brand-specific assets, such as styling and policies.
Note: The framework and implementation layers are relative separations of application assets. The designation of an asset as belonging to either the framework or implementation layer depends on the design of the application. An implementation application for one line of business may belong to the framework layer for another application. For example, a large financial services company creates an auto loan application for a specific division or brand. A second division then extends the application, customizing assets as necessary. For the second division, the original auto loan application is part of the framework layer. For the first division, the application is part of the implementation layer. Pega Platform application types Pega Platform™ provides you several options to create new applications. You can build on an existing application, which allows you to save development time by reusing key elements, such as case types or data types. You can build a new application without a built- on application by selecting Build from scratch from the New Application wizard. Note: You can access the New Application wizard from Dev Studio by clicking Application menu > New Application.
1.- Theme Cosmos
This application type is best for new applications to take advantage of a non-React Pega Cosmos design system. Theme Cosmos, like Cosmos React, offers an implementation of Pega’s Cosmos design system but the architecture and capabilities of each differ. Theme Cosmos uses section- based UI and offers all Pega Platform capabilities. Select the Theme Cosmos application type to ensure your application can use all capabilities. Theme UI-Kit When you select the Theme UI-Kit option to create a new application, the new application uses the latest UI-Kit design system, instead of the Cosmos design system. Pega does not recommend using Theme UI-Kit to create a completely new application. While usable and documented into the foreseeable future, the UI-Kit does not receive continued design effort. The UI-Kit is now considered a legacy product. Cosmos React This application type is best for new applications to take advantage of low-code and team collaboration using ReactJS and the latest client-side rendering engine. Cosmos React UI currently prioritizes known usage patterns and high priority use cases and configurations. As of 8.6, Cosmos React does not support all features from earlier releases of Pega Platform, including rule delegation, localization, and mashup. Select the Cosmos React application type if your new application does not require all capabilities. For example, if you are building a new low-code application from the beginning and want to take advantage of the most updated UI and functionality, you might choose to build a Cosmos React application. However, if your business requires localization across multiple languages, you would choose to build a Theme Cosmos application, which provides this capability. Por ejemplo, si está creando una nueva aplicación de código bajo desde el principio y desea aprovechar la interfaz de usuario y la funcionalidad más actualizadas, puede optar por crear una aplicación Cosmos React. Sin embargo, si su empresa requiere la localización en varios idiomas, optaría por crear una aplicación Theme Cosmos, que proporciona esta capacidad.
Cosmos React This option provides a Cosmos-based design system for use in a ReactJS-based run-time architecture. From the process perspective, when you select Cosmos React from the New Application wizard, the updated framework allows most of your development work to occur in the low-code App Studio environment of Pega Platform by using OOTB tools and components. The Cosmos experience simplifies your development work with streamlined interactions and a modern interface. For example, in a medical claim upgrade case, navigating on a single screen expedites the user's workflow. By minimizing screen-to-screen navigation, users avoid the disorienting jump to a new screen in the middle of a process. Additionally, the Cosmos experience allows you to preview items, such as cases, in the same screen. The Cosmos React design gives you: Improved data visibility Enhanced case processing Customizable columns Focus on relevant data The ability to instantly modify values and perform quick actions on table rows Cosmos design is recommended for new applications to build a highly efficient and robust system. Note: Performance-wise Cosmos React runs two to three times faster than Cosmos Rules due to fewer transferred resources (Javascript and CSS).
Theme Cosmos with section-based UI
This option builds your application on Cosmos rules, such as the application template Theme-Cosmos 3.01, a non-React version of Cosmos. For example, in the GoGoRoad application, the application definition uses the Theme-Cosmos 3.01 built-on application. Cosmos rules introduce significant improvements to the user experience. The chief enhancements include: A new case preview panel Flexible screen space management An improved search experience The ability to open and work with several independent sessions of your web application Increased efficiency when working with multiple cases CUESTION Pega UI Kit is the most advanced, feature-rich, low-code option for creating a new application in Pega Platform. <FALSE> UI Kit is now a legacy design. Developers are encouraged to build in low-code by using Cosmos.
