How can I add a parameter of type object (non-array) to the "Call Web Service" integration tool for a SOAP request?
Hi Community,
I'm having troubles generating a request with the following XML body, using the "Call Web Service" integration tool.
<soapenv:Envelope xmlns:soap="" xmlns:cam="" xmlns:soapenv=""> <soapenv:Header /> <soapenv:Body> <cam:startProcessCampanhasaaaaa> <soap:request> <soap:agencia>1</soap:agencia> <soap:argumentarioVenda>A</soap:argumentarioVenda> <soap:nomeCampanha>A</soap:nomeCampanha> <soap:nomeEntidade>A</soap:nomeEntidade> <soap:notasAdicionais>A</soap:notasAdicionais> <soap:numeroEntidade>A</soap:numeroEntidade> <soap:requestId>A</soap:requestId> <soap:validadeTarefa>1</soap:validadeTarefa> <soap:gestorEntidade>A</soap:gestorEntidade> </soap:request> </cam:startProcessCampanhasaaaaa> </soapenv:Body> </soapenv:Envelope>
Basically, when I tried to add the necessary parameters for the request, I've noticed that I can't add an object parameter without defining it as an array.
This setting is blocking me from following the structure of the request above. Because the "request" parameter is not an array. I also tried to import the wsdl, and it didn't work either.
Is there a way to bypass this? Should I create a script task instead?
Thank you in advance.
Best Regards,
Pedro Pinheiro
Like
Hello,
You can create this service manually.
Because this is an OOTB behavior with the value "is array".
Hi Kalymbet Anastasia,
Sorry, but I didn't understand your answer. The property "Is array" is true by default.
Do I need to create the soap request using a script task?
Best Regards,
Pedro Pinheiro
Pedro Pinheiro,
Yes, you're right. When the request parameter is of type object the collection is considered a typed array and the checkbox is checked by default and not editable.
In this case, using a script task for the SOAP service would solve the case.
BR,
Bhoobalan Palanivelu.