We don't support multipart/mixed OOTB. We only support multipart/form-data via the use of pyRequestAttachmentPage.
If you do want to work with a scenario specific to
multipart/mixed
, then you can use REST connector to construct such a request. These are the changes you need to make:
1) First, understand how multipart works. Read this:
https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
2) In REST Connector POST request header, set Content-Type to multipart/mixed;boundary=<enter any set of alphanumeric chars here>, say multipart/mixed;boundary=
abc
3) Manually construct the POST request body as below and set the entire value to a string property, say, pyNote:
--
abc
Content-Type: application/json
<blank line here>
<your JSON body goes here>
<blank line here>
--
abc
--
4) In REST Connector POST Message Data section, select Map from as Clipboard and Map from key as .pyNote.
In the above example, "abc" is used as boundary separator between each "part". You just need to construct one part for your requirement.
******** Edited by Moderator Marije to add recommended documentation *********
The above solution is specifically aimed for unsupported multipart/mixed scenario.
We don't support multipart/mixed OOTB. We only support multipart/form-data via the use of pyRequestAttachmentPage.
If you do want to work with a scenario specific to
multipart/mixed
, then you can use REST connector to construct such a request. These are the changes you need to make:
1) First, understand how multipart works. Read this:
https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
2) In REST Connector POST request header, set Content-Type to multipart/mixed;boundary=<enter any set of alphanumeric chars here>, say multipart/mixed;boundary=
abc
3) Manually construct the POST request body as below and set the entire value to a string property, say, pyNote:
--
abc
Content-Type: application/json
<blank line here>
<your JSON body goes here>
<blank line here>
--
abc
--
4) In REST Connector POST Message Data section, select Map from as Clipboard and Map from key as .pyNote.
In the above example, "abc" is used as boundary separator between each "part". You just need to construct one part for your requirement.
******** Edited by Moderator Marije to add recommended documentation *********
The above solution is specifically aimed for unsupported multipart/mixed scenario.
The content type "multipart/form-data" should be used for submitting forms that contain files, non-ASCII data, and binary data.
For the latest documentation on implementing a generic use case to send attachment through connect Rest rule please check the following:
File attachment configuration in REST and SOAP integrations
Use case: Send file attachments from a repository
Mapping the data for a POST response for a Connect REST rule
*******************************************************************************************
We don't support multipart/mixed OOTB. We only support multipart/form-data via the use of pyRequestAttachmentPage.
If you do want to work with a scenario specific to multipart/mixed , then you can use REST connector to construct such a request. These are the changes you need to make:
1) First, understand how multipart works. Read this: https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
2) In REST Connector POST request header, set Content-Type to multipart/mixed;boundary=<enter any set of alphanumeric chars here>, say multipart/mixed;boundary= abc
3) Manually construct the POST request body as below and set the entire value to a string property, say, pyNote:
-- abc
Content-Type: application/json
<blank line here>
<your JSON body goes here>
<blank line here>
-- abc --
4) In REST Connector POST Message Data section, select Map from as Clipboard and Map from key as .pyNote.
In the above example, "abc" is used as boundary separator between each "part". You just need to construct one part for your requirement.
******** Edited by Moderator Marije to add recommended documentation *********
The above solution is specifically aimed for unsupported multipart/mixed scenario.
We don't support multipart/mixed OOTB. We only support multipart/form-data via the use of pyRequestAttachmentPage.
If you do want to work with a scenario specific to multipart/mixed , then you can use REST connector to construct such a request. These are the changes you need to make:
1) First, understand how multipart works. Read this: https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
2) In REST Connector POST request header, set Content-Type to multipart/mixed;boundary=<enter any set of alphanumeric chars here>, say multipart/mixed;boundary= abc
3) Manually construct the POST request body as below and set the entire value to a string property, say, pyNote:
-- abc
Content-Type: application/json
<blank line here>
<your JSON body goes here>
<blank line here>
-- abc --
4) In REST Connector POST Message Data section, select Map from as Clipboard and Map from key as .pyNote.
In the above example, "abc" is used as boundary separator between each "part". You just need to construct one part for your requirement.
******** Edited by Moderator Marije to add recommended documentation *********
The above solution is specifically aimed for unsupported multipart/mixed scenario.
The content type "multipart/form-data" should be used for submitting forms that contain files, non-ASCII data, and binary data.
For the latest documentation on implementing a generic use case to send attachment through connect Rest rule please check the following:
File attachment configuration in REST and SOAP integrations
Use case: Send file attachments from a repository
Mapping the data for a POST response for a Connect REST rule
*******************************************************************************************