Question
April Technologie
FR
Last activity: 12 Jan 2018 7:32 EST
Personal Ruleset not in Ruleset Stack in "Application Requestor"
Hi,
I have a problem with the personal ruleset. For my project, in test environnement, I would like to change temporarly several rules just for one technical operator. This technical operator is used only to call somes Services PEGA.
To do this, I add an access group Administrator to this operator and set it as the default access group. I connect with this operator to open the designer studio and change the rules in its private ruleset. If I call the Service PEGA with this operator, the change works fine and PEGA executes the rules in the private ruleset.
If I change the default access group to set the old value (without portal and with other roles), PEGA don't execute the rules in the private ruleset. The private ruleset is ignored and I don't know why.
It's very surprising because if a have a user portal to this my access group and if I connect, I can see that the ruleset stack contains the private ruleset.
So my conclusion is :
- In a browser requestor, the private ruleset is visible
- In an application requestor (when I use the operator to call a Service), the private ruleset is not visible. I don't understand that.
Do you have any idea ?
Regards,
Kévin
***Updated by moderator: Lochan to update Categories***
Pegasystems Inc.
IN
When you call a service, the service runs on a different operator i.e. operator mentioned in the authentication profile. So the rules in private checkout may not be visible.
Could you check with which operator the service is being executed. May be a log in service activity can get the operator information.
April Technologie
FR
Thank you for your response. Yes, I call the service PEGA with the good operator. I've defined 2 tags to send the user and password.
Moreover :
- If I call the service with my operator and with the default access group of it as an administrator (the access group used to change the rules in the private ruleset), it works fine. The service used the rules changed.
- If I call the service with the same operator and with the default access group of it as other than the administrator (my real access group with restrict authorization), it doesn't work. The private ruleset is not used.