Discussion
Ruleset Prerequisites
Hi Team,
In the below 3 bullet points, could you please explain the third one with an example? What is the need for the system assembling all lowered number ruleset versions of a ruleset (Let us say Ruleset X) and rulesets included in the same major version, when we save a rule in a ruleset X.
I am not able to understand what is the need of this 3rd poing when we save a rule.
Rule validation is performed against the prerequisites. When we save a rule, the system assembles a complete required ruleset version list from:
- All ruleset versions on this list
- All ruleset versions listed as prerequisites for those ruleset versions
- All lower-numbered ruleset versions of this ruleset and the rulesets included in the same major version
Hello Mohan,
Good question.
Point 3 is alluding to the fact that rule resolution does not include rules that are in a lower major version. Noted a little further below in the article:
"Note that rules in versions below the major version are not visible to rule resolution. For example, if you list Alpha:02-01-01 that depends on Beta:02-01-01, Alpha:02-01-01 won’t see rules in Beta:01-XX-XX."
So if you have rules in Beta:01-XX-XX there is an expectation that the skimming refactoring tool was used to skim the needed/used rules from Beta:01-XX-XX to Beta:02-01-01 when that major version was created. Reducing the number of rules that are no longer used or replaced due to versioning. Faster and more efficient for rule resolution.
I hope this helps clarify,
Tara, Pega Academy Support Team