What logic does Pega execute to suggest the RuleSet when I try to create a copy of any rule using 'Save As'. I have noticed that it doesn't always suggest the same ruleset as original ruleset where the rule is being saved from, even if that ruleset is accessible. This behaviour does lead some developers to save rules in incorrect ruleset sometimes.
One workaround that I have found is to do a private checkout and then try to checkin that rule in latest ruleset version - this way Pega always suggest exact same ruleset as original ruleset. However, this method is not ideal as working a private checkout in a big team is not ideal. Also private is only available on locked rulesets.
***Updated by Moderator: Marissa to update categories; add enhancement ID***
this normally gets displayed using a dropdown in the section pzChangeReuleset under @baseclass.
The source of the dropdown is a datapage D_pzAvailableRuleSetsForRecord which takes Application Name, version etc as input parameter. This data page in turn uses pzFilterAvailableRuleSetsForRecord activity to create the list.
So if you go thru this activity , you will understand the logic.
Generally it gives you the available ruleset lists and it is advisable that the developers pay attention while saving any rules. If you want to stop or prevent this mistakes, one possible way out could be the use of branching ruleset instead of doing private checkout etc.
Thanks for your response Santanu. I'll have a look at the activity. Howeve, I think that the logic should be to implicitly suggest the same ruleset as original one as the first choice, because that's normally what a developer wants to do. However, if a developer wants to move the rule to a different ruleset they would be explicitly making that choice upon 'Save As' anyway.