Connect REST: pass query-params in message body
I need to use REST Connector to simulate a file upload. The raw request should look like below
POST <scheme>://<host>:<port>/<path>/upload HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: multipart/form-data; boundary="----=_Part_23_27316591.1476188379376"
MIME-Version: 1.0
Content-Length: 477
Host: <host>
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
------=_Part_23_27316591.1476188379376
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="FormElement"
575885858
------=_Part_23_27316591.1476188379376
Content-Type: text/plain; charset=Cp1252; name=today.txt
Content-Transfer-Encoding: binary
Content-Disposition: form-data; name="today.txt"; filename="today.txt"
abc
def
------=_Part_23_27316591.1476188379376--
The above request is created using soapUI. When I add a query parameter in my connect rest, it appends the parameter in query string. I need it to be send in the message body. Please suggest a way to achieve this.
Pegasystems Inc.
US
Are you trying to achieve what can be done here by soapUI: https://www.soapui.org/rest-testing/understanding-rest-parameters.html? If yes, what version of pega are you using?
Pegasystems Inc.
US
Query parameters members of a query string, so the behavior you describe is correct.
You are not looking to "pass query params in the message." What you are showing in your example is a multipart message.
Pega does have support for creating multipart messages but it requires some extra effort. If you search the PDN for "multipart" you will find many posts about this topic.
This document describes the simplest case, which is a 1-part message: https://community.pega.com/support/support-articles/unable-send-attachment-connect-rest
This offiical help documentation describes the mechanism in use: https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
Capgemini
IN
Hi,
Thanks for these links but these are talking about including the attachments in the request which I have undesrtood. My problem is for the other part of the request as below
------=_Part_23_27316591.1476188379376
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="FormElement"
575885858
Along with the file I have to send the value of this element (FormElement) which is one of the fields needed during the file upload. I tried to include this as a query parameter but then this gets appended in the url (like below) not appears in the body as above.
POST <scheme>://<host>:<port>/<path>/upload?FormElement=3543253252 HTTP/1.1
Pegasystems Inc.
US
You are mistaken. The posts are talking about setting up the request attachment page so that Pega will create a multipart message as part of the request. Pega's connector does not currently provide a UI for setting up multipart messages, so populating the request attachment page is the method by which the mutlipart message is constructed.
Capgemini
IN
Sorry for the confusion but I am not talking about any UI for setting up the multipart messages. My rest connector has to achieve the functionality of a browser file upload as mentioned in https://www.soapui.org/rest-testing/understanding-rest-parameters.html. Along with file content, I have to pass a field call "FormElement" which is sort of an identifier of the the uploaded file.