Question
Wipro
IN
Last activity: 19 Nov 2018 13:29 EST
Overriding Circumstanced Rules
RSV 01-02-xx - my base rule exists
RSV 01-03-61 - Have done property based circumstance checking D_PortalContextGlobal.pyActiveWorkGroup ="XXX"
RSV 01-03-62 - Have update circumstanced rule in RSV61
Note: RSV 61, RSV 62 and RSV01-02-XX are locked and promoted to higher environment.
Now, as per business requirement, we need to circumstance this rule based on user roles; not on work group.
To override existing circumstanced rules, I tried following things. But, unable to override.
1) I saved as circumstanced rule(which is in RSV62) in RSV64 and withdrawn.
2) Saved as base rule to RSV 64 and checked Base Rule Check box.
3) Tried circumstancing(property based) the base rule in RSV64 using the function HaveRole. I am getting error saying the rule is already circumstanced based on .pyActiveWorkGroup and I cannot override with another property.
Please advise.
***Edited by Moderator Marissa to move from Pega Academy to Pega Support Community; update platform capability tags***
Accepted Solution
Coforge Technologies (Erstwhile Incessant Technologies)
GB
- A rule cannot be a circumstance if another rule of the same type and name exists in a different class, even if the classes are unrelated and have no inheritance relationship, even if the conflicting rules are set to withdrawn rule. This is because the Apples To class of a rule is not taken into account when looking for conflicting circumstance rule instances, only the name.
Pegasystems Inc.
US
While this question applies a concept we learn about in the SSA course it is not an exercise and as such I don't have an answer readily available. I would however remind you that a couple of other things that could be affecting your withdrawing of the circumstanced rules is the apply to class, the same qualifiers and last make sure the rules are checked in as this will have an affect on rule resolution.
In addition, I would recommend this post be moved to Pega Support Community where more resources may be available to give you some additional insight.
Sean
Pega Academy Self-Study Support Team
Accepted Solution
Coforge Technologies (Erstwhile Incessant Technologies)
GB
- A rule cannot be a circumstance if another rule of the same type and name exists in a different class, even if the classes are unrelated and have no inheritance relationship, even if the conflicting rules are set to withdrawn rule. This is because the Apples To class of a rule is not taken into account when looking for conflicting circumstance rule instances, only the name.