Discussion

4
Replies
4961
Views
 Mohan Kumar (MohanK54)
Cognizant technologies solution

Cognizant technologies solution
US
MohanK54 Member since 2014 15 posts
Cognizant technologies solution
Posted: June 15, 2015
Last activity: November 15, 2016
Posted: 15 Jun 2015 3:07 EDT
Last activity: 15 Nov 2016 17:35 EST
Closed

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
Pega Academy
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 Discussion, please write a new Discussion.
Posted: 6 years ago
Posted: 15 Jun 2015 13:16 EDT
Tara Pottebaum (pottt)
PEGA
Tech Enablement, Lead Curriculum Developer
Pegasystems Inc.
US


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
Posted: 4 years ago
Posted: 15 Nov 2016 17:35 EST
sankararao kottavalasa (sankararaok5408)
Capgemini

Capgemini
IN

Hi Pottt,


Just want to confirm if the 3rd bullet


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

is supposed to say All lower-numbered ruleset versions of this ruleset included in the same major version instead of All lower-numbered ruleset versions of this ruleset "and" the rulesets included in the same major version.


Thanks.


Sankar


 
Posted: 5 years ago
Posted: 24 Jun 2015 23:33 EDT
Ashok Kumar Bommisetty (Ashok_Bommisetty)
Areteans Technology

Areteans Technology
IN

Hello MohanK54,


 


Lets say you are saving a rule in Alpha:02-05-01 which has a reference to the section in Alpha:02-04-22 and this section has a reference to a property in Beta:02-04-20.


 


Assume pre-requisites of Alpha:02-05-01 is Beta:02-05-01.


 


So in design time validation, the system checks the validations on every ruleset version of Alpha:02-xx-yy,Beta:02-xx-xx and the pre-requisites of Beta and so on.  This is a cyclic form of validation since your new rule can have reference to any rule within the scope of the ruleset.

 


Thanks,


Ashok