Application Rules and Rulesets Flashcards

What do Pega 'production levels' control for rulesets?

Answer: A numeric setting (1–5) that determines which rules are editable in a given environment, restricting changes in production

Production levels (1–5) on rulesets restrict rule editing in environments configured with a matching or higher level, protecting production rules.

What is the 'Application Settings' rule type used for in Pega?

Answer: To store environment-specific configuration values that can vary per deployment without altering rule logic

Application Settings rules externalize configurable parameters (like feature flags or endpoint URLs) so they can change per environment without touching logic rules.

What are Pega 'Guardrails', and how do they relate to ruleset quality?

Answer: Best-practice guidelines built into Pega that evaluate rules for compliance and flag violations to maintain ruleset quality

Pega Guardrails are embedded best-practice checks that evaluate rules and report violations, helping development teams maintain high-quality rulesets.

What is the key architectural consideration when sharing a ruleset across multiple Pega applications?

Answer: The shared ruleset's classes must exist in the class hierarchy of all consuming applications for proper rule resolution

Rule sharing relies on class hierarchy — a rule is only resolved for an application if its 'Applies To' class exists in that application's class tree.

What distinguishes a 'framework' application from an 'implementation' application in Pega?

Answer: A framework application provides reusable generic rules and patterns; an implementation application contains customer-specific overrides

Framework applications encapsulate reusable, industry-agnostic patterns; implementation applications extend them with business- and client-specific customizations.

In a Pega application record, what is the 'ruleset list'?

Answer: The ordered list of ruleset versions included in the application, defining their priority in the rule resolution stack

The ruleset list in an application record specifies which ruleset versions are part of the application and their priority order in the resolution stack.

When a developer saves a new rule in Pega, which ruleset receives the new rule by default?

Answer: The highest-versioned unlocked ruleset that the developer has access to in the current application

Pega defaults to saving new rules into the highest unlocked ruleset available to the developer in the current application context.