Posted: 16 Oct 2015 19:08 EDT Last activity: 4 Nov 2015 7:28 EST
What is best way to avoid moving unwanted classes during deployment
When we create a product and include individual rule sets, all the classes mentioned in that rule set will get added. This is creating problem in below scenario,
Suppose we have created a class in XXX rule set and 01-01-02 version where as there is some other functionality in 01-01-01 version. When we move XXX 01-01-01 rule set to higher environment, all the classes in that rule set get added which is not desirable.
To solve this either we need to select advance option and deselect check box for individual rule. or we need to select Exclude Non Rule Resolved Rules check box while creating product (when selected this option, rule set version is not getting moved).
Can anybody suggest what is best way to solve this?
To get around this issue, pick the RuleSet version alone using the individual instances to include option, and migrate single ruleset version rule. Followed by this import your original package with other rules
i think, copying rules will not help. Product rule includes all the classes in the mentioned rule set is the problem. Also including rule set version alone and then moving other rules can be work around.
But better if issue can be addressed in future versions of the pega.
How about selecting "Exclude non resolved rules" for the xxx ruleset and then add pzInskey of non resolved rules belonging to xxx, if this scenario is applicable for one or two etc.? And if there are multiple such rulesets then consider option suggested by Chunzhi.