Application Rules and Rulesets Flashcards

What is a 'built-on' (prerequisite) application in Pega?

Answer: A parent application whose rulesets are appended to the current application's stack, enabling rule inheritance

A built-on application is a parent layer whose rulesets are appended below the current application's own rulesets in the stack, supporting inheritance.

When you 'override' a rule from a built-on application in Pega, what actually occurs?

Answer: A new rule instance with the same name is created in the higher-priority application's ruleset, taking precedence during resolution

Overriding creates a new rule in the top application's ruleset; because it appears higher in the stack, it is found first, leaving the original untouched.

What is an 'application overlay' pattern in Pega?

Answer: Extending a shared framework application by creating overriding rules in a customer-specific implementation application

Application overlay is the practice of specializing a framework or shared app by overriding selected rules in a higher-priority implementation layer.

What happens to your application when you update the version reference of a built-on (prerequisite) application in the application record?

Answer: Your application's ruleset stack now includes the newer version of the built-on application's rulesets, giving access to updated rules

Updating the prerequisite version reference causes Pega to include the new version's rulesets at resolution time, exposing new and changed rules.

What is the role of the Pega Platform application (formerly PegaRULES) in the built-on application chain?

Answer: It is the ultimate base application at the bottom of every application's built-on chain, providing all core platform rules

Pega Platform is the foundational base application that every Pega application ultimately inherits from, housing all core platform rules.

Which Pega view helps you identify which rules in your application are inherited from a built-on application versus locally defined?

Answer: The Application Overlay view, which visually distinguishes inherited from overridden rules

The Application Overlay view shows a layer-by-layer breakdown of which rules are inherited versus locally defined or overridden.

What is the recommended best practice for the depth of a built-on application chain in Pega?

Answer: Keep the chain shallow (around 4–5 levels) to balance reusability with maintainability and avoid performance impacts

Pega best practices recommend limiting the built-on chain to roughly 4–5 levels to prevent complexity and performance issues.