Is it possible to change namespace on SOAP Response?

[Thiagofmeira]

Hi All,

After the customer sends any SOAP Message to our instance, servicenow answers with the following XML.

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <SOAP-ENV:Body>
      <Fault>
         <Detail>
            <faultInfo causingMessageId="ba713a3b-acbd-4c13-a331-d821384d3e21" causingOperation="error" class="SUPPORT" code="STN_SN_INM_ba713a3b-acbd-4c13-a331-d821384d3e21" kind="TECHNICAL" timestamp="2022-05-19T12:37:07.144Z">No incident was found with the provided BackboneID</faultInfo>
         </Detail>
         <Reason>
            <Text xml:lang="en">Please provide a BackboneID</Text>
         </Reason>
      </Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The customer has concerned that their system cannot read the namespace:

xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"

and he says it should be like:

xmlns:env=http://www.w3.org/2003/05/soap-envelope

Does anybody know if it is possible to change it? I have even tried to pass that as a string on the response creation, but it seems the structure on the first line is built-in by servicenow automatically.

Any idea? 

Thanks

[Ankur Bawiskar]

Hi,

Can you explain what type of API endpoint it was and what change and where did you do that change?

Regards
Ankur

[Thiagofmeira]

Hi,

That was a SOAP integration with a legacy bus system.

We had to use a static WSDL that the customer provided because they could not adapt their system to SN. With that we had to make an scripted web service and an include to process all inbounds from their system(and their bizarre namespaces) using the static WSDL. Also, we had to script the normal outbounds.

Regards

Thiago