To override the Content-type in your clients, use the HTTP Accept Header, append the .soap12 suffix or ?format=soap12
HTTP + SOAP12
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /soap12 HTTP/1.1
Host: equipstage3.e-isg.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<GetMobile_Workflow_Transaction_Sync_Data xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<UserID>String</UserID>
<WorkflowID>String</WorkflowID>
</GetMobile_Workflow_Transaction_Sync_Data>
</soap12:Body>
</soap12:Envelope>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<Mobile_Workflow_Transaction_Sync_Data_Result xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<Mobile_Workflow_Transaction_Sync_Data>
<Mobile_Workflow_Transaction_Sync_Data>
<Is_Sync_Request_Processed>false</Is_Sync_Request_Processed>
<Mobile_Workflow_Transaction_Sync_ID>String</Mobile_Workflow_Transaction_Sync_ID>
<Sync_Request_Processed>String</Sync_Request_Processed>
<Sync_Request_Recieved>String</Sync_Request_Recieved>
<Sync_Request_Result>String</Sync_Request_Result>
<Transaction_JSON>String</Transaction_JSON>
<WorkflowID>String</WorkflowID>
</Mobile_Workflow_Transaction_Sync_Data>
</Mobile_Workflow_Transaction_Sync_Data>
</Mobile_Workflow_Transaction_Sync_Data_Result>
</soap12:Body>
</soap12:Envelope>