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.

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.

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.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope 
	xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
	xmlns:ns0="http://schemas.microsoft.com/dynamics/2010/01/datacontracts" 
	xmlns:ns2="http://schemas.microsoft.com/dynamics/2008/01/services" 
	xmlns:ns1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" 
	xmlns:ns4="http://schemas.microsoft.com/dynamics/2008/01/sharedtypes" 
	xmlns:ns3="http://schemas.microsoft.com/dynamics/2008/01/documents/Customer">
	<SOAP-ENV:Header/>
	<SOAP-ENV:Body>
		<ns2:CustomerServiceCreateRequest xmlns="http://schemas.microsoft.com/dynamics/2008/01/services">
			<ns3:Customer xmlns="http://schemas.microsoft.com/dynamics/2008/01/documents/Customer">
				<ns3:CustTable class="entity">
					<ns3:Currency>USD</ns3:Currency>
					<ns3:CustGroup>group</ns3:CustGroup>
					<ns3:Name>SL_Name_3123</ns3:Name>
					<ns3:DirParty xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
						class="entity" xsi:type="AxdEntity_DirParty_DirOrganization">
					<ns3:Name>dirparty_SL_3123</ns3:Name>
					</ns3:DirParty>
				</ns3:CustTable>
			</ns3:Customer>
		</ns2:CustomerServiceCreateRequest>
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

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.