The Ruleset list
The ruleset list
While ruleset validation governs rule development and import, the ruleset list, sometimes referred to as the ruleset stack, governs rule execution at run time. Because ruleset validation is enforced during development, the system does not need to validate the rulesets during run-time processing.
The ruleset list indicates the rulesets that are available to the application for a given operator session. The ruleset list is available in the operator profile Operator > Profile.
The ruleset list is assembled by Pega when an operator logs in to the application. The process begins by locating the versioned application rule referenced on the access group of the operator.
The ruleset list consists of rulesets referenced on the application form. The built-on applications are processed repeatedly until the PegaRULES application is located.
The ruleset list is built by stepping through the built-on applications until the PegaRULES application is located. First, the PegaRULES ruleset list is added to the ruleset list. Then the built-on applications are processed recursively adding each application’s ruleset to the ruleset list on top of the previously added rulesets.
For example, the PegaRULES application is at the base, the HRFW application is built on top of PegaRULES, and the HRApps application is built on top of HRFW.
If you are allowed to check out rules, a personal ruleset is added to the top of the list. The personal ruleset has the name of the operator ID and contains the rules checked out by the operator.
The ruleset list for the application with built-on applications can be viewed on the ruleset list landing page (Dev Studio > Configure > Application > Structure > RuleSet Stack).