Ruleset stack is not building and not picking the check out rule at runtime
Hi, When I check out a rule to make the necessary changes and try to test my changes, it is not picking the check out rule. When I verify the profile, it is not showing the ruleset stack and even tried to verify in the tracer, and it is not showing the check out ruleset (with username). Tried to restart the application, but still not picking the check out rule. We are using PRPC v7.2 for our application.
Please share your thoughts!
Regards,
Kiran
***Updated by moderator: Lochan to add SR details***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
US
Hi Kiran,
You mentioned that when you verify the profile, it is not showing the ruleset stack. Are you saying that you do not see your private ruleset listed in your profile?
Virtusa Corp.
IN
Yes CarissaW_GCS, it is not showing my private rule set and any other rule set in the stack.
Pegasystems Inc.
US
Please open an SR and an engineer can work with you on the issue.
Pegasystems Inc.
IN
Hi Kiran,
Please let us know if you do log an SR for this and its ID. That way we can track it and follow-up this discussion with the resolution.
Thank you,
Virtusa Corp.
IN
Hi Lochan_DV,
We have already raised the SR -- SR-B66348 for this issue.
Pegasystems Inc.
IN
Thanks Kiran,
I have updated the original post above with this information. I also see that the SR is being actively investigated.
Regards,
Pegasystems Inc.
IN
Hi,
Could you please attach operator profile screen shot.
Virtusa Corp.
IN
Hi yapas,
Here is the screenshot of operator profile.
Accepted Solution
Pegasystems Inc.
IN
Hello,
The SR was resolved with the below suggestion.
During logout, PRPC resets a requestor with a new SessionAuthorization populated with contexts of access groups defined in BROWSER requestor type. If multiple customer specific entries are included the authorization context is not set correctly.
Removing customer specific Access Groups from the list so the correct context is utilized for authorization resolves the issue.
Thanks!