Document that conforms to the input view schema of the Snap (the Target Schema column in Mapper or Structure Snap).

• Mapper
• JSON Generator
• File Reader

Document which represents the SOAP response (an XML transformed into JSON).

• Mapper
• JSON Formatter
• REST Post

Required. Specify a unique name for the Snap. Modify this to be more appropriate, especially if more than one of the same Snaps is in the pipeline.

Default value: SOAP Execute

Example: http://www.webservicex.net/stockquote.asmx?WSDL

Example: http://www.webserviceX.NET/}StockQuote

Example: {http://www.webserviceX.NET/}StockQuote

Example: GetQuote

Default value: 0

Example: 0

Default status: Deselected

If you select this checkbox:

• The value in the Default value for substitution field is used for substitution if the elements don't exist in the incoming documents. If not selected, or if there are no incoming documents, the elements for which the incoming documents don't have any values will be deleted from the SOAP request.
• The Preserve input empty values field is ignored.

Default status: Deselected

Default status: Deselected

Default status: Deselected

Default status: Deselected

Default status: Deselected

Default status: Selected

The following example shows how contents of the file, salesforce_sample.csv, are inserted into the SOAP response and what updates are required to the Snap.

Note that to reference the attached file; you must specify the following line of code in the SOAP envelope:

<xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include"  
href="cid:<Content-ID_of_the_filename>"/>

Default status: Deselected

Default status: Deselected

Default status: Deselected

Default status: Deselected

Specify an action to be taken when a SOAP call returns an empty response. The default action is Output no documents.

You can handle SOAP call with an empty response in the following ways:

• Output no documents: The Snap executes successfully and returns no output document.
• Output empty document: The Snap executes successfully and returns an empty document in the output view.
• Write error document: The Snap execution fails and returns an error document in the error view.

Default value: Output no documents

Example: Output empty documents

Default value: 3

Example: 5

Default value: 2

Example: 5

Example: (with expression toggle on) $['SOAP-ENV:Body']['ns2:orderResponse']['ns2:result'] == "success"

This would match the success criteria in this SOAP response:

[
  {
    "SOAP-ENV:Body": {
      "@xmlns:SOAP-ENV": "http://schemas.xmlsoap.org/soap/envelope/",
      "ns2:orderResponse": {
        "@xmlns:ns2": "http://www.Snaplogic.com/Snapbox/order",
        "ns2:result": "success",
        "ns2:transactionId": "533822"
      }
    }
  }
]

You can see that the user can find the SOAP output by setting Snap Execution on the SOAP Execute Snap, then seeing what comes out. You can also hook up a Mapper Snap and see the schema there. You can do that on the input view, but not the output view.

Any content that needs escaping from Velocity editor parsing can be enclosed with the following syntax:

#[[ <data> ]]#

See https://velocity.apache.org/engine/1.7/vtl-reference.html#unparsed-content for more information.

Default status: Deselected

Default status: Deselected

Default status: Deselected

Default status: Selected

If a SOAP endpoint does not support 'Chunked transfer encoding', this property should be set to 'Calculate content length'. If the endpoint responds with an error of HTTP status code "411 Length Required", the Snap automatically retries the request with 'Calculate content length' mode.

Default value: Chunked transfer encoding

Example: Calculate content length

This property enables Snap execution over HTTP. Use the appropriate library to utilize the latest SOAP capabilities. The available options are:

• Apache HttpComponents
• Apache CXF

Default value: Apache CXF

Example: Apache HttpComponents

Default value: Execute only

Default value: Validate & Execute