Declare Page not populated for SOAP Connect by Agent
It was observed that when an Agent move a work object to reach a SOAP Connect step, the SOAP URL didn't get populated. The SOAP URL is stored in a dynamic system setting and was supposed to be loaded using a Declare Page. The SOAP connection failed due to the declare page not getting the correct value.
It was reported by the customer that an error message was thrown by InvokeAxis2 activity.
Steps to Reproduce
Create a flow where it has an assignment with an SLA, followed by a utility shape to make a SOAP connection.
In the SLA's escalation activity, make a call to ResumeFlow activity.
In the SOAP Connect rule, set the SOAP URL to be =Declare_SomePageName.pyEndpointURL
The activity triggered by the declare page will then have Apply-DataTransform that loads the URL from a dynamic system setting using @(Pega-RULES:Utilities).getDataSystemSetting
The root cause of this problem is a defect in Pegasystems’ code/rules. The SOAP URL was not able to access the declare page because the access group was using SLA agent's access group.
The following local change has been suggested:
1) Go to the activity that the SOAP connect rule calls. Add a parameter pzUseCurrentAccessGroupForChild.
2) In the first step of the activity, set the value of Param.pzUseCurrentAccessGroupForChild to true.
This local change has only been tested in house and found to have addressed the issue.
0% found this useful