Support Article

SOAP call fails due to operation name



For Connect-SOAP rules, the operation name is set by Pega to the the method name of the Service SOAP rule. If the Service SOAP rule has the same name as the original WSDL file's operation name, the service call fails with the below error.

Error Messages

Failed to retrieve Rule-Service-SOAP instance MFT.Services.postFile using access group Dec:Administrators

Steps to Reproduce

Create a Service SOAP rule and use a message format with a root node that does not match the service method name.

Root Cause

An issue in the custom application code or rules is identified as root cause of the issue.


Here’s the explanation for the reported behavior: 

If "Specify custom SOAP action URI" checkbox is selected and SOAP action URI is used for SOAPAction to be included in the request then Service Method Name has to be same as the Operation Name.
If the SOAP Action header field is empty or does not match the pattern that is specified in the service WSDL document.
Suggest Edit

Published September 10, 2016 - Updated October 8, 2020

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.