Completely control SOAP XML Request Body Swagger EPCIS GS1

Hey there, When developing a published web service, I found out that Mendix pre-populates a number of attributes in the soap request and response. For example, when adding a single text attribute, the SOAP request looks like this: <soap:Envelope xmlns:tns="" xmlns:xsi="" xmlns:soap="" xmlns:xsd=""> <soap:Header/> <soap:Body> <tns:MRO_Add> <SingleAttribute>exampleString</SingleAttribute> </tns:MRO_Add> </soap:Body> </soap:Envelope> For a client I am investigating whether it is possible to completely control the SOAP request body, so as to be able to conform to a standard (EPCIS) defined by GS1. This standard defines that the request body should look like this: <?xml version="1.0" encoding="UTF-8"?> <!--Sample XML file generated by XMLSpy v2021 (x64) (> <epcis:EPCISDocument xmlns:cbvmda="urn:epcglobal:cbv:mda" xmlns:rail="" xmlns:epcis="urn:epcglobal:epcis:xsd:1" xmlns:xsi="" xmlns:n1="" xmlns:sbdh="" schemaVersion="0" creationDate="2001-12-17T09:30:47Z" xsi:schemaLocation="urn:epcglobal:epcis:xsd:1 EPCglobal-epcis-1_2-railMRO-noext.xsd"> <EPCISBody> <EventList> <ObjectEvent> <eventTime>2001-12-17T09:30:47Z</eventTime> <eventTimeZoneOffset>+01:00</eventTimeZoneOffset> <epcList> <epc>urn:epc:id:giai:1234567.7911bg</epc> </epcList> <action>ADD</action> <bizStep>urn:epcglobal:cbv:bizstep:commissioning</bizStep> <disposition>urn:epcglobal:cbv:disp:active</disposition> <readPoint> <id>geo:41.6725,-86.255278</id> </readPoint> <extension> <ilmd> <rail:additionalTradeItemID tradeItemIDTypeCode="BUYER_ASSIGNED">(SAPEAM)11804102</rail:additionalTradeItemID> </ilmd> </extension> </ObjectEvent> </EventList> </EPCISBody> </epcis:EPCISDocument> Question: is there a way to get rid of/adapt the standard SOAP request body so we can conform to the standard? Thanks for thinking along! Best regards, Wouter
1 answers

Have you tried the Custom Request Template?

For even more control, you could consider using the Call REST Service activity. It allows you to POST to any URL with any HTTP body.