The order of the entries within these lists affects the assembly of a user's RuleSet list and the operation of the rule resolution algorithm.When assembling the RuleSet list at sign-on, the system works from the top of each list down. RuleSets appear in the following order, in two layers.
The operator's personal RuleSet, containing rules the operator has checked out, comprises the top of the second layer. (This RuleSet is not specified on the Application rule form. Operators have a personal RuleSet only if the Allow Rule Check Out? check box (on the Security tab of their Operator ID data instance) is selected.
Branch RuleSets form the next lower group in the second layer.
Application RuleSets form the next lower group in the second layer.
Component and shared RuleSets, if any, form the next group of the second layer.
Standard RuleSets provided by Pegasystems, that start with the five-character prefix "Pega-" (not the four-character prefix "Pega"), appear at the bottom of the second layer.
***Updated by moderator: Lochan to close post*** This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Share this page
Moderation Team has archived post,
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
describes how to see your current RuleSetList and goes into greater detail about the layers. In fact it mentions two layers as well, then proceeds to describe 8 layers in a table.
It is more important that you understand how your ruleset list is generated in your own application. If you are confused about how your particular ruleset list was created, showing us this specific ruleset list and your concern would be easier to explain.
Additionally using the application > structure > ruleset stack can give further details (but omits some of the info from the final ruleset list) including the particular version numbers of the rulesets in a hierarchical view based on your application contributions to your ruleset list.