Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Different results when calling Report-based SOAP service

SA-24093

Summary



A SOAP service is designed. Depending on the option chosen when testing, "Use current requestor context" or "Initialize service requestor context," the outcome is different even if both options use same user details.
The SOAP service calls an activity to run a report definition having the "Report on descendant class instances" selected.

Error Messages



Not Applicable

Steps to Reproduce



1. Create a SOAP service.



2. Create activity.



3. Create report.



4. Run SOAP.


 

Root Cause



A defect in Pegasystems’ code or rules:
The authorization does not switch correctly if the user's AccessGroup is matched with service package AccessGroup. Authorization switches only when the requestor is fetched from the pool, but after authentication the condition in Authorization.setActiveAccessGroup() method stops doing the complete switch and application level properties are not set.

Resolution



Apply HFix-27801.

Published June 7, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us