SOAP Execute

In this article

Breaking change for Pipelines using the SOAP Execute Snap

Before the 4.25 release, the SOAP Execute Snap was used to preserve the empty XML elements in the envelope irrespective of selecting the Preserve input empty elements checkbox.  After upgrading to 4.25 GA, the Snap might fail due to missing empty XML elements. In such cases, select the Preserve input empty elements checkbox to resolve the issue. If the failure persists then contact the support team.

Snap type:



This Snap calls the SOAP endpoint using the incoming data and writes out a SOAP response.

  • Expected upstream Snaps: References in the generated envelope can be mapped using a Mapper or Structure Snap.
  • Expected downstream Snaps: The Snap will output one document for every SOAP response, hence any document processing Snap can be used downstream.
  • Expected input: Document that conforms to the input view schema of the Snap (the Target Schema column in Mapper or Structure Snap)
  • Expected output: Document which represents the SOAP response (an XML transformed into JSON)

Clicking Customize Envelope will attempt to generate a SOAP envelope based on the information defined in the properties and the selected WSDL. The action will launch the XML Editor.


 In general, you will most likely always use Customize Envelope

All files referred to in WSDLs hosted in SLDB must be either explicit URLs or relative in the same project. For example, if the WSDL refers to an XSD "Projects/SomeSchema.xsd", this must be changed (in the WSDL) to refer to the file in the same project "SomeSchema.xsd", and the XSD should be put in that same folder.  

The envelope will be stored in the Snap after clicking OK. Further, the envelope can be exported to SnapLogic's file system using the export action or be imported from there using the import action. The Generate template action will regenerate the template, but the content of the editor must be removed prior to that. The envelope can be customized to meet specific endpoint needs. The Snap is fully configured and executable once the envelope is finalized.  

The generated envelope will have velocity references in it. These references (here, $session_id) will be exposed to the Target Schema column of the upstream Mapper or Structure Snap. However, any changes made by the user in the generated envelope won't be reflected to this Target Schema column. In this case, the user has to remember the references added/modified in the generated envelope to map them in the upstream Snap.

Template generation only works with document-style WSDLs. RPC-style WSDL template generation is currently not supported.

To execute a create request through an NTLM account in the SOAP Execute Snap, use the generic envelope similar to the following sample. This ensures the output is rendered as excepted. See the example for a demo on how this works.

Only a sample envelope

This sample is meant only for reference purposes and must not be replicated.

In the upstream Mapper or Structure Snap, these references can be mapped to static values (such as 1234) or to the references exposed in the Input Schema column. 

We map the reference session_id in the upstream Mapper (Data) Snap in the example below. Note that the content of the editor must be saved prior to selecting the schema upstream.


The SOAP Execute Snap is a writing Snap. The Snap can be executed during preview to allow executing the defined request and to retrieve data and schema from the response. The SOAP Snap can be executed during the save operation by enabling the Snap Execution option.

If you receive the following error: "reach the innerElementCountThreshold:50000", perform one of the following tasks:

  • Configure the Global Properties of the Groundplex in the file ("/opt/snaplogic/etc/" in Linux; "c:\opt\snaplogic\etc\" in Windows) to increase the threshold value:
    jcc.jvm_options = -Dorg.apache.cxf.stax.maxChildElements=<value>
    where 'value' is 1000000 or higher. OR
  • Add the same line as a global property in the node.

These properties are available only in a Groundplex.

How to use the default value for substitution

To use the Default value for substitution property of the Snap:

  1. Provide a value for Default value for substitution. This value is placed between the leaf elements—the elements that don't have any child elements.

    The substitution won't work if these leaf elements are contained within an array that does not exist in the incoming documents.

  2. Select the Use default value for substitution property.


Incoming document:

Here, the session_id element doesn't exist in the incoming document. In this case, using Default value for substitution will give us the following envelope: 

<?xml version="1.0" encoding="UTF-8"?> 
	<SOAP-ENV:Envelope xmlns:SOAP-ENV="" 
			<SOAP-ENV:Header /> 
					<session_id>NO VALUE</session_id> 

If you don't specify the Default value for substitution and don't select the Use default value for substitution property, the elements will be removed from the envelope recursively.


Support and
  • Works in Ultra Pipelines if timeout is specified.
  • After upgrading your Snaplex to 4.20 GA version, Pipelines with SOAP Execute Snap that uses the Apache CXF library might hang without executing. The Snap using HTTPComponents library executes successfully.

Breaking Change

The HTTP header field's behavior in the SOAP Execute Snap is changed. Specifying only a key is not sufficient. Both key and value must be provided when invoking a task. 


This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Configuring SOAP Accounts for information on setting up this type of account.

InputThis Snap has at most one document input view.
OutputThis Snap has at most one document output view.
ErrorThis Snap has at most one document error view and produces zero or more documents in the view.

Snap Settings

Field NameDescription


Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.


Specify the URL for the WSDL.

WSDL File URL is case sensitive.


Service Name*

Specify the system function that has been exposed to Web-based protocols.

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


Specify the endpoint (in WSDL 2.0 terminology)/Port name (in WSDL 1.1 terminology).

Whenever presented with multiple port versions, always select the latest one.



Specify the operation to invoke



Specify the timeout for the web service call (in seconds). 0 indicates no timeout.

Default value: 0
Example: 0

Encode Attribute

Select this checkbox to differentiate the attributes from XSD with an '@' prefix in the input schema and "at-" prefix in the template.

Default value: Deselected

Default value for substitution

This value will be used for substitution for the leaf elements which are not objects and/or not enclosed in an array. If nothing is specified and Use default value for substitution is selected, an empty string will be used for substitution.

Use default value for substitution

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 value: Not selected

Preserve input empty values

Select this checkbox to preserve any empty value within the input data in the SOAP request. If you select Use default value for substitution checkbox, then this field is ignored. 

Include root element 

Select this checkbox to include root element in the body or header in the keys generated in the envelope template.

Default value: Not selected

Trust all certificates

Select this checkbox to trust all certificates, such as self-signed certificates.

Default value: Not selected 

Remove illegal characters

Select this checkbox to remove illegal UTF characters based on XML 1.0 standard.

Default value: Not selected

Escape special characters

Select this checkbox to enable the Snap replace the XML special characters  in XML template variable values with the respective character entity references (&gt; &lt;, and so on) while inserting these values into the Apache Velocity template. For example, the Snap replaces < with &It;

The special characters that the Snap escapes are: >, <, &, ', "

Default value: Selected.

Enable MTOM 

Select this checkbox to enable content processing to multipart, application/xop+xml type.

When Message Transmission Optimization Mechanism (MTOM) processing is enabled, binary files will be transmitted outside the SOAP request envelope as a MIME attachment. XML-binary Optimized Packaging (XOP) should then be used to reference the attachment within the SOAP request envelope.

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.

After selecting the Enable MTOM Processing field, the following updates to the Snap are required for successful execution:  

  • Attachments: Specify the Binary filename (salesfoorce_sample.csv), and its Content-ID and Content-Type.

    With MTOM processing enabled, entering attachment part value to the Part field is:

    • Mandatory if you are using the Apache HttpComponents library.
    • Optional if you are using the Apache CXF library.
  • Customize Envelope: Click Customize Envelope to update the SOAP envelope to import the attached file and its contents.

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

<xop:Include xmlns:xop=""  

Default value: Not selected

Output SOAP envelope

Select this checkbox to output the whole SOAP envelope instead of just the SOAP body
Default value: Not selected

WS Addressing

Creates and configures an addressing feature with the use of addressing requirements. It enables WS-Addressing, that is it supports WS-Addressing but does not require its use. It also configures to accept all the response types.

Default value: Not selected

Output HTTP response headers

Select this checkbox to output the HTTP headers in the response.

Default value: Not selected

SSL Protocol

Advance setting, leave blank to allow Java default.

Response to null SOAP call return value*

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
ExampleOutput empty documents

Maximum request attempts

Specify the maximum number of attempts to be made to receive a SOAP response. The SOAP request is terminated if the attempts do not result in a SOAP response. If no value specified, only 1 attempt is made before terminating a SOAP request.

Default value: 3
Example: 5

Retry interval

Specify the interval between two successive SOAP requests. A retry happens only when the previous attempt resulted in an exception. 

Default value2
Example: 5

Success condition

An expression to match success criteria in the SOAP response.

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": "",
      "ns2:orderResponse": {
        "@xmlns:ns2": "",
        "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.

Customize envelope

Launches the XML editor which will generate a SOAP envelope based on the defined properties, WSDL URLService namePort name and Operation. The editor will load an envelope if it was defined previously. The editor allows you to save SOAP envelopes in SnapLogic's file system or import existing SOAP envelopes from it. The /wiki/spaces/AP/pages/1438085 template can be used to pass dynamic values from upstream Snaps.

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

#[[ <data> ]]#

See for more information.

HTTP header

Use this field set to define HTTP header key-value pairs.

You must provide both key and value when invoking a task.


Use this field set to add attachments.

Allow duplicate headers

Select this checkbox to allow duplicate headers value. If not selected, then the last value of the duplicate header key is used.

Default Value: Not selected

Standardize error output

Select this checkbox to view the document in error view (a standardized error document will show up in the error view)—error, reason, resolution, stack trace and original.

Default value: Not selected

Route all exceptions to error view

Select this checkbox to route the Snap exceptions generated by WSDL Url, Service Name, Endpoint and Operation properties to the error view and successfully execute the pipeline execution.

Default value: Not selected

Import WSDL documents

Select this checkbox to import the external documents while reading the WSDL file. The files that are declared with tag name wsdl:import & xs:import are retrieved and processed. If this checkbox is not selected, then the external documents that are required for WSDL are ignored.

Default value: Selected

Transfer type

The Snap uses each input document as a body of one SOAP request. There are two ways of transferring the request body to the endpoint: 'Chunked transfer encoding' or 'Calculate content length'. If 'Chunked transfer encoding' is selected and when the message size is greater than 4KB, the SOAP request will be sent using chunked transfer encoding. Otherwise, the request will not be chunked and the Content-Length header will be included in the request.

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

Library API

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

We recommend using HttpComponents, because Apache no longer maintains CXF v2.

Snap execution

Select one of the three modes in which the Snap executes. Available options are:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.
  • Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.
  • Disabled: Disables the Snap and all Snaps that are downstream from it.

Default value: Execute only
Example: Validate & Execute

Managing Data Cache Duration

Whenever you provide resources, such as WSDLs and XSDs, in SOAP-based Snaps, SnapLogic caches the data for some time. The default cache duration is four hours. You can modify this to any positive number by updating the global properties for the Snaplex. See Configuration Options for information on defining the cache duration. 

This is not applicable when the SOAP Snaps call a third-party SaaS, such as NetSuite, since the cache duration is determined by the SaaS. 

See it in Action


Create a new record in MS Dynamics AX using SOAP Execute Snap

This example demonstrates how you can use the SOAP Execute Snap to create records in MS Dynamics AX.

The Mapper Snap creates the input JSON for the SOAP Execute Snap through a series of mappings.

The SOAP Execute Snap uses the JSON input to create a new record in the MS Dynamics AX through a SOAP POST request. It uses the generic envelope to populate the fields in the endpoint.

 The image below shows a preview of the output:

This output shows the result of the create operation and also populates the original dataset under original key.

Mapping of Variables from Target Schema to SOAP Execute Envelope Template

This example will help you in understanding about the working of envelope template variable substitution using Include root element check box.

Let us take an example where we are making a call to the login operation for Salesforce's SOAP API (WSDL). 

Here is the pipeline consisting a Mapper Snap and SOAP Execute Snap with credentials defined as Pipeline parameters.

Upon validating the pipeline, Target Schema will be defined for the Mapper. Once this is available, we can define the Target path variables from the Target Schema.

Here, in the SOAP Execute Snap, we are checking the Include root element checkbox which ideally is not checked by default.

Upon regenerating the template we can observe the expected and correct variable substitution being performed.

Also, as we have included the Debugging output, we can see the correct substitution.

For more info, see Using the debug Output View

Using the debug Output View

You can add a second output view named debug (all lower-case) to view the details of the SOAP request. For every SOAP call, the Snap writes two separate output documents to the debug view.  The first document contains the request headers and envelope. The second document contains the response data.

For example, consider the following SOAP Execute Snap with two output views:

Below is a snapshot of the output from both output views:

output0 (default output)

See Also

Snap Pack History

 Click to view/expand
ReleaseSnap Pack VersionDateTypeUpdates
February 2024main25112 StableUpdated and certified against the current SnapLogic Platform release.
November 2023main23721 StableUpdated and certified against the current SnapLogic Platform release.
August 2023434patches22655 Latest

Fixed an issue with the SOAP Execute Snap that caused it to be unable to parse some WSDL files.

August 2023




Updated and certified against the current SnapLogic Platform release.

May 2023main21015 StableUpgraded with the latest SnapLogic Platform release.
February 2023432patches20553 Latest
  • Fixed the storage issue with the JCC output file caused by the cyclic import of WSDL warning logs by SOAP Snaps.

  • The performance of the SOAP Execute Snap has been enhanced by reducing the need for multiple WSDL downloads and parsing to obtain the same Description.

February 2023main19844 StableUpgraded with the latest SnapLogic Platform release.
November 2022main18944 StableUpgraded with the latest SnapLogic Platform release.
September 2022430patches18332 Latest

The SOAP Execute Snap now does not display the null pointer exception when parsing the given WSDL to generate the Customize Envelope.

August 2022430patches17325 Latest
  • The patch 429patches17186, previously deployed for the SOAP Execute Snap caused an error (the failure of the getOrderStatus operation) even when the WSDL is valid. With the latest patch, this Snap generates the customized envelope without errors when you upload a valid WSDL
  • The SOAP Execute Snap does not throw a Null Pointer Exception when using the Import Schema'.

August 2022main17386 StableUpgraded with the latest SnapLogic Platform release.
4.29 Patch429patches17186 LatestFixed an issue with the SOAP Execute Snap where the Snap displayed an error when a valid WSDL getOrderStatus SOAP operation was uploaded.





Upgraded with the latest SnapLogic Platform release.

4.28main14627 StableUpgraded with the latest SnapLogic Platform release.





Upgraded with the latest SnapLogic Platform release.
StableUpgraded with the latest SnapLogic Platform release.
4.25 Patch425patches10994

Enhanced the SOAP Snap Pack to support HTTP Proxy Authentication.

4.25 Patch425patches10152

Enhanced the SOAP Execute Snap with a new checkbox Escape special characters that enable the snap to escape XML special characters in XML template variable values when this Snap inserts these values into the Apache Velocity template.

StableUpgraded with the latest SnapLogic Platform release.
4.24 Patch424patches9077
  • Fixes the incremental thread count issue in the SOAP Execute Snap by ensuring that only instance of SoapCustomAsyncHTTPConduitFactory should pass throughout the execution of the Snap.
  • Fixes the issue in SOAP Execute Snap where the Snap failed as the default value of Content-Type field had been modified after upgrading the Snap in 4.24 release.
StableUpgraded with the latest SnapLogic Platform release.
4.23 Patch423patches7411-Latest

Enhances the SOAP Execute Snap by including an additional output view. When named debug (all lower-case), the Snap outputs the SOAP request headers, envelope, and the output document that is written to the default output view. 


Upgraded with the latest SnapLogic Platform release.

4.22 Patch422patches6770

Enhances the SOAP Execute Snap by adding WSSE header to support SOAP WSSE Account with Apache HttpComponents library.

4.22 Patch422patches6656

Fixes the SOAP Execute Snap failure due to different character sets used in the HTTP request data.

StableUpgraded with the latest SnapLogic Platform release.
4.21 Patch421patches6040

Requires the use of a generic envelope while executing a create a request through an NTLM account in the SOAP Execute Snap to ensure the output is rendered as expected.


Enhances SOAP Execute, by making it necessary to provide both key and value under the HTTP header field while invoking a task.

4.20 Patchsoap8816

Enhances the SOAP Execute Snap to allow user-specified empty fields in the SOAP request.

4.20 Patchsoap8762
  • Fixes the SOAP Execute Snap to:
    • Successfully handle redirected requests, when the WSDL file specifies an HTTP URL which redirects SOAP requests to an HTTPS URL.
    • Successfully generate the schema even if the XSD does not contain the <types> element.  
4.20 Patchsoap8712

Fixes the SOAP Execute Snap where the Snap throws an NPE error when generating a SOAP request template.

4.20snapsmrc535-StableUpgraded with the latest SnapLogic Platform release.
4.19 Patchsoap8642-Latest
  • Fixes the SOAP Execute Snap where the Snap encounters the following issues:
    • The Snap throws NPE when generating a SOAP request template.
    • The Snap throws the following error when making a SOAP call, if the SOAPAction HTTP header contains a stringDoes not match an operation.
4.19 Patchsoap8375-Latest

The SOAP Snaps have a Library API field. When the selected value is the non-default HTTP Components, there was a breaking change in the structure of the output response document between 4.19 GA version (snapsmrc528) and the latest patch version (soap8375). We recommend that if you want to use the non-default (non-CXF) value for Library API, then you must use this latest patch version as subsequent GA releases may result in Pipeline executions failing. 

If your current or new Pipelines use CXF as the Library API value, or do not handle SOAP response bodies greater than 1000 lines, or do not rely on NTLM authentication, then you can continue using your existing Snap Pack version (stable distribution – snapsmrc528).


Adds the Library API field to the SOAP Execute Snap to enable execution over HTTP. The supported libraries are Apache HttpComponents and Apache CXF, and both the libraries support the Message Transmission Optimization Mechanism (MTOM).

4.18snapsmrc523-StableUpgraded with the latest SnapLogic Platform release.
4.17 PatchALL7402-Latest

Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.


Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during the preview check box.

4.16 Patchsoap6886-Latest

Fixed an issue with the SOAP Execute Snap wherein SLDB protocols were not being supported.

4.16 snapsmrc508-StableUpgraded with the latest SnapLogic Platform release.
4.15 Patchsoap6726-Latest

Fixed an issue with the Soap Execute Snap failing for Workday when the Trust All certificate is enabled while using SSL authentication.

4.15 Patchsoap6699-Latest

Fixed an issue with the SOAP Execute Snap wherein errors where not getting routed to the error view and pipeline execution was failing.

4.15 Patchsoap6269-Latest

Removed synchronization from a WSDL service of SOAP Execute Snap to avoid hangs.

4.15 Patchsnapsmrc500-StableUpgraded with the latest SnapLogic Platform release.

4.14 Patch


Removed the hardcoded timeout in ClientBuilder.

4.14 snapsmrc490-StableUpgraded with the latest SnapLogic Platform release.
4.13 Patchsoap5214-Latest

Fixed a bug in the SOAP Execute Snap wherein the end tag is removed incorrectly when generating the envelope.

4.12 Patchsoap5064-Latest
  • Fixed an issue with the SOAP Execute Snap that is unable to parse the XML schema information from the given WSDL.
4.12 Patchsoap4899-Latest
  • Fixed an issue with the SOAP Execute Snap, which hangs a pipeline at that Snap.

  • Added a new property in SOAP Execute "Include root element" that when enabled, provides the target schema. 

4.12 Patchsoap4821-Latest

Fixed a null pointer exception that displays while generating the SOAP templates.


Added the property Exception To Error View to the SOAP Execute Snap to route the Snap exceptions to the error view.

4.11 Patchsoap4648-Latest

The SOAP Execute Snap now handles the WSDL child elements referencing the root schema element when generating envelope templates.


Updated support of NTLM Account Authentication to SOAP Snap Pack.

4.10 Patchsoap3964-Latest

Fixed an issue with the Soap Execute Snap that fails with error "Failure:Error:Unable to parse XML schema information from the given WSDL"

4.10snapsmrc414-StableUpgraded with the latest SnapLogic Platform release.
4.9.0 Patchsoap3113-Latest

Addressed the issue: Error: Could not find the schema component' while generating custom envelope

4.9.0 Patchsoap3090-Latest

Addressed an NPE on Envelope generation in SOAP Execute Snap.

4.9snapsmrc405-StableUpgraded with the latest SnapLogic Platform release.
4.8.0 Patchsoap2966-Latest

Addressed an issue where Soap Execute Snap was unable to parse WSDL from CapGemini

4.8.0 Patchsoap2783-Latest

Addressed an issue with SOAP Execute Snap throwing an HTTP Response '404: Not found' error.

4.8.0 Patchsoap2719-Latest

Added the WS Addressing property to the SOAP Execute Snap.

4.8.0 Patchsoap2699-Latest

Removed the null values from the header during configure phase.

4.8.0 Patchsoap2703-Latest

Fixed performance issue on SOAP Snap Pack which was caused by the WSDL imports.

  • Added support in the SOAP Snaps for WSDLs with import elements.
  • Added the Info tab to accounts.
4.7.0 Patchsoap2522-Latest

Addressed an 'Error: Could not translate an element declaration element' during envelope generation issue in the SOAP Execute Snap

4.7.0 Patchsoap2251-Latest

Addressed error while getting instance of Description for complex WSDLs.

4.7.0 Patchsoap2215-Latest

Support multiple namespaces in WSDLs.


Updated the SOAP Execute Snap with a new property, Standardize error output.

4.6.0 Patchsoap2123-Latest

Resolved an issue where importing xsd files over https did not use proper authorization.

4.6.0 Patchsoap2064-Latest

A Gzip Interceptor was added to the SOAP client to uncompress Gzipped responses.

4.6.0 Patchsoap1932-Latest

Implemented a new property "Standardize error output " for the backward-compatibility.

4.6.0 Patchsoap1856-Latest

Resolved an issue in SOAP Execute when handling null field.

  • Enhanced SOAP Execute Snap to handle a SOAP call with an empty response. 
  • Resolved an issue in SOAP Execute Snap that failed with an error in returning a response but returns an empty response. 
  • Resolved an issue in SOAP Execute Snap that caused the Snap to unsuccessfully parse XML schema from a valid WSDL when generating a SOAP envelope.
  • SOAP Execute Snap is updated to terminate a SOAP request after a number of attempts, and to successfully execute the Snap only if a success condition is met. The fields added are Maximum request attempts, Retry interval, & Success condition. For more information, see SOAP Execute.
  • Enhanced error handling in SOAP Execute Snap when generating customize envelope.

Resolved an issue in SOAP Execute Snap that occurred when connecting to ServiceNow.

Known Issue

  • Soap Execute Snap: This Snap currently does not support the wsdl:import statement. For wcf, the way to generate a single wsdl for a wcf wsdl url which ends in ?wsdl, is to change it to ?singleWsdl.
  • Soap Execute Snap now returns HTTP header in output
  • Support WS-Security Draft 13 for a SOAP WSSE Account
  • Resolved an issue with SOAP WSSE Account. Authentication was rejected because <wsu:Created> DateTime value is not being correctly converted to UTC timezone.
  • Resolved a null pointer exception.
  • Added thread safety to XML library to prevent Null pointer exception.
-September 5, 2015 (4.2.2)--
  • Support added to return SOAP headers in SOAP Execute Snap.
  • Resolved an issue with SOAP Execute being unable to interpret MTOM response SOAP responses.
  • Migration impact: Output SOAP Envelope now defaults to false.
  • New setting: SSL Protocol
-August 7, 2015--
  • SOAP Execute Snap now disables importing XSDs if any are in a WSDL.
  • Resolved a Null pointer exception in SOAP Execute.
  • Resolved an issue with not being able to generate a template from Taleo WSDL.
  • Resolved a loader contraint violation issue in SOAP Execute when resolving method "org.apache.http.impl.client.HttpAuthenticator".
  • Resolved an issue with WSSE Account not working with SOAP Execute Snap
-June 27, 2015--
  • Timeout option required for SOAP Execute Snap.
  • Support for SOAP attachments.
-June 6, 2015--

SOAP Execute: resolved an issue with the SOAP WSSE account not working

-May 15, 2015--
  • SOAP Request failed for Hiperos WSDl
  • SOAP Execute: failure, resolution is not provided; Not loading issue
  • SOAP Snap failed for control character created by CSV Parser
  • SOAP Snap: updated error message when an invalid WSDL was selected
  • SOAP Snap output schema updated. Error and reason were added back to the output in addition to Fault code, detail entry, soap fault exception, and fault string

May 2, 2015


SOAP Snap: enhanced template generation

-January 2015--
  • WSSE Account type added.
  • Optional Trust all certificates property added.
-October 18, 2014--

Soap Execute does not work with Basic Auth header during configure phase

-September 5, 2014--

SOAP Execute: Encode Attribute was added as an optional setting for this Snap. When selected, the attributes from XSD will be differentiated with an '@' prefix in the input schema of this Snap.

-June 30, 2014--
  • Addressed the following issues:
    • SOAP Request: Default value should be given in the SOAP binding type property instead of blank.
    • SOAP Request: Document should be updated with SOAP Binding type Property.
    • SOAP Execute not generating the full template - including some required fields for D&B V2 services
    • SOAP Execute Snap: Write the envelope to the error view for debug purpose
    • SOAP Execute Snap fails to generate template
-May 2014--

SOAP Request updated to support input parameters in HTTP headers

-November 2013--

SOAP Request Snap

-August 2013--

SOAP Call Snap