The legacy SOAP Message activity uses SOAP messages defined in the System Web Services plugin and can call the messages using a MID Server.

This activity is deprecated in the Vancouver release and no longer shows up in the Workflow canvas for new workflow development. New workflows should use the Orchestration SOAP Activity templates instead.

Existing workflows using it will continue to work as designed. To edit this activity in an existing workflow, you must re-activate the activity.

Input variables

Table 1. SOAP Message activity input variables
FieldParameterDescription
SOAP Message soap_message The SOAP Message defined under the System Web Services plugin's Outbound SOAP Message [sys_soap_message] table. (System Web Services > Outbound > SOAP Message)
SOAP Message Function soap_message_function The function to call that is defined in the SOAP Message. Functions are listed in the SOAP Message Functions related list in each SOAP Message record.
SOAP Endpoint soap_endpoint Endpoint to use instead of the SOAP endpoint value in the SOAP Message Function record. Leave this field blank to use the defined endpoint in the SOAP Message Function record.
Variables variables Variables to substitute into the SOAP Envelope defined in the SOAP Message Function record. Use this format for the string: 
name1=value1, name2=value2, . . .
If either the name or value contains a comma or equal sign, escape these characters with a backslash.
Use MID Server use_midserver Check box for using a MID Server to send the SOAP message. A MID Server might be necessary to reach an endpoint within a firewall or a sub-network that is not visible from the instance. If this check box is selected (true), but no MID Server is defined in the MID Server field, Workflow automatically attempts to find a MID Server.
MID Server midserver Name of the MID Server to use. This field appears when you select the Use MID Server check box. The workflow ignores this parameter if the use_midserver parameter is disabled.
Sensor Script sensor_script The script to execute after the request has been made and a response has been received. You can access the full XML response body from the activity.output object.