The building blocks of Pega applications
Rules can be combined in many ways to achieve unique results.
Rules
In a Pega application, the most basic reusable building block is the Rule.
Rules describe the features and behavior of individual cases, such as how the user interface is displayed, or when work urgency should increase. You use rules to build basic applications by using out-of-the-box Pega features and capabilities.
Some other examples of Rules include flows, UI elements, data pages, integrations, decisions, conditions, and SLAs.
Modules
Modules contain collections of Rules that address a specific business, integration, or utility purpose.
Adding Modules to your enterprise reuse library enables teams to build more complex applications, but in an easier way. It is important to understand the business needs and how those needs map to reusable Modules, so that you can build up a reuse library that delivers strong ROI. The right level of granularity to your Modules is critical to their wide-spread reuse.
Modules are consumed in Dev Studio and App Studio by development teams, often in the Case Designer, by using Relevant Records and Configuration Sets. For more information on Relevant Records, see Relevant records for rule reuse. For more information on Configurations Sets, see Creating a configuration set.
Applications
A Pega Application is a collection of Rules and Modules that generate production-ready workflow automation solutions. Use Pega Platform's Situational Layer Cake to enable further contextual specialization.
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?