Support Article
Incorrect guardrail warning in Access Role to Object Rule form
SA-20436
Summary
When editing access of an access role to an object, there are multiple incorrect guardrail warnings regarding the privilege rules that are referenced in this Rule-Access-Role-Obj instance. The privileges come from the Pega-DecisionManager ruleset. Though the application ruleset has the Pega-DecisionManager ruleset in its stack, it is showing the guardrail warning.
Error Messages
The privelige py[PRIVELIGENAME] does not exist or is not visible from the ruleset of this Rule-Access-Role-Obj instance.
Steps to Reproduce
- Create a Rule-Access-Role-Obj instance.
- In the "Privileges" tab use an out of the box (OOTB) privilege rule (e.g. “pyMonitorInteractionHistory”) from the “Pega-DecisionManager” ruleset.
- Save the Rule-Access-Role-Obj rule.
Root Cause
There is an issue in the step 3 (java step) of the activity "CheckForWarnings" of class "Rule-Access-Role-Obj" RuleSet "Pega-RULES:07-10-15".
Resolution
This issue is scheduled to be resolved in update release Pega 7.2.1.
Published March 4, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.