Question

i have 10 versions of same rule defined but i want a 2nd version to be picked not latest version in pega how to do it

Hi All,

"i have 10 versions of same rule defined (1 to 10 versions) ,but i want 2nd version to be picked and not latest version(10)" Please let me know how to achieve this.

one way that i can think is to save the 2nd version into the latest version - this works if the version 10 is unlocked - what if the rulessets are locked ? - create a new rule (replica of version 2 and save into version 11 ??!!!)

As according to my understanding, if i have to choose availability as "No" then i have to set availability as "No" all the way from version 10 to 3, if i have to choose option of "Blocked" all the chain of rule will be blocked making rule unavailable.

Comments

Keep up to date on this post and subscribe to comments

April 19, 2018 - 2:11am

Hi,

If you choose the Availability of the rule "Not Available" from 3 to 10,  then rule 2 will be picked. 

However, if suppose you blocked the rule say 9, rule 10 will still be picked at rule resolution. 

To know more about rule resolution, please refer the below link.

https://pdn.pega.com/sites/pdn.pega.com/files/help_v731/procomhelpmain.htm#search-Rule%20resolution

I would also recommend you to go through Senior System Architect, this topic has been discussed in detail there. Hope it helps.

Regards,

Rachit 

January 14, 2019 - 1:55am

It depends on factors such as your application stack, ECS, availability etc.   

Based on the contact you can always save it in most specific class and the top most RSV. 

January 14, 2019 - 5:51am

make 2nd version of rule as final availbility thats it.

July 5, 2019 - 6:44am
Response to KiranChandraC2242

kiran chandra if you make final then we cant save as to other ruleset but in same ruleset we can save as to higher verion so whatever you said it wont work

March 11, 2019 - 2:16am

You can also save the 2nd version in the Production ruleset  

March 12, 2019 - 6:46am

You can checkout 2nd version of the rule into a branch ruleset and include the branch in your application stack.Once you have confirmed changes on top it and the rule is ready to be moved to production you can merge it into the desired ruleset version .

I believe , if you had used branching concepts . You would have not ended up creating 8 more versions. 

Assumption is you are trying the above in a non-prod environment

There you go !!

Thanks

Harish

March 18, 2019 - 9:41am

You can check Effective Start Date field in the Ruleset but it will apply on the all the rules in that particular ruleset version.