Call SOAP Web Service

The Call SOAP Web Service action sends a SOAP XML request to a web service and returns the web service's SOAP XML response. The response is either presented in XML (or HTML) form as the current page or set as the value of an XML variable.

As SOAP requests can be quite complex, you will typically use an external tool to generate the request and paste it into the SOAP XML Request property. The request can be dynamically altered by specifying XML from Expression to create a template SOAP request substituting literal values by expressions.

If the web service returns a SOAP fault, the message is not returned by the action. Instead, the action will generate an error which can be handled using the standard error handling mechanisms.

Properties

The Call SOAP Web Service action can be configured using the following properties:

Web Service URL: The location of the web service operation is specified here. Web services generally use the HTTP protocol. The value can be specified in several ways using the Value Selector.
SOAP Action: This property can contain an optional SOAP action. The value can be specified in several ways using the Value Selector. The SOAP action is sent as part of the HTTP headers. The SOAP action is typically, but not always, a URL specifying the requested action
SOAP Request: This property must contain a valid SOAP XML request. By default the XML can be specified literally. To dynamically create the SOAP XML request you can choose XML from Expression or XML from Variable.
SOAP Version: This property specifies which version of the SOAP specification to use for sending the SOAP request. SOAP 1.1 and SOAP 1.2 are supported. When specifying SOAP 1.1 the Content-Type will be set to text/xml and the (optional) SOAP Action will be set using an additional HTTP header. When specifying SOAP 1.2 the Content-Type will be application/soap+xml and the (optional) SOAP Action will be set as the action parameter of the Content-Type HTTP header.
Preemptive Auth: Enable to pre-send the authorization header to accelerate the authorization process. When preemptive authentication is enabled, Design Studio sends the Basic or Digest authentication response before the server returns a 401 Unauthorized response. To use preemptive authentication, you need to configure default credentials in the robot settings.
When using the Digest authentication, each algorithm has two variations: session and non-session. A non-session algorithm is defined as <name>, such as SHA-256, and non-session is defined as <name>-sess, such as SHA-256-sess.
Output: Choose whether to output the SOAP response as an XML page or as the value of an XML Variable. In robots created with Kofax RPA 7.2 or earlier, this may be Output Result as HTML Page, meaning that the XML will be transformed to an HTML representation.
Options: The robot's options can be overridden with the step's own options. An option that is marked with an asterisk in the Options Dialog will override the one from the robot's configuration. All other options will be the same as specified for the robot.