Support for Multipart Request Body

A multipart/form-data request body contains a series of parts that are separated by a boundary delimiter, which is constructed that uses Carriage Return Line Feed (CRLF), "--", and also the value of the boundary parameters. The boundary delimiter must not appear inside any of the encapsulated parts.

Each part has the Name, Type, Content-Type, and Part ID fields.

--BOUNDARY
Content-Type: application/json
Content-Disposition: form-data; name="job"

{
"object":"Contact",
"contentType":"CSV",
"operation":"insert"
}
--BOUNDARY
Content-Type: text/csv
Content-Disposition: form-data; name="content"; filename="content"
(Content of your CSV file)
--BOUNDARY—

While adding a custom action, for example, for the Freshservice Create Child Ticket With Attachments operation, you can click Attachments to view the list of all the configured parts to be sent to the service provider. You can send a multipart/form-data payload, which contains either a file, or text, or a document type.

The parts to be sent to the service provider appear in the input signature. All options including the Add option to add a custom part are disabled if the resource is not of type of multipart/form-data. Currently, multipart/form-data payload is supported only at the request level, that is, only in the input signature.

• Name - Name of the file part as documented in the SaaS provider API documentation.
• Content Type - Content type of the part's content (if the Type is TEXT), or the file you are uploading (if the Type is FILE) or the serialization type to which the document will be serialized and become the part content (if the Type is DOCUMENT).
• Type - IBM webMethods Integration defines the following three-part types:
  • TEXT - Represents a simple text part of a multipart/form-data payload where the content of the part is of type text/plain. You can use this part to send raw text data as the content of a part, in a multipart request. From a file upload perspective, this part is used to convey extra information about the upload behavior, like target folder paths/folder names where the file must be uploaded.
  • DOCUMENT - Some back ends expect application/JSON or application/xml content in the part body. This represents a part where the content of the part is of the type application/JSON or application/xml.
  • FILE - Represents a binary part of a multipart/form-data payload where the content of the part is binary or the content of the file itself. To upload a file, you will normally use this part. For file upload use cases, this part is the main or mandatory part that is required by the service provider.

• Active/Inactive - Represents whether this part will be included as part of the service signature.

For some connectors and operations, for example, for the Salesforce ^R Bulk v2 Data Loader connector and createAndUploadDataUsingMultipart predefined operation, IBM webMethods Integration supports multipart request body.