Override or set custom value for boundary in an outbound integration - HTTP multipart/form-data

Hi Harish

Here is a similar thread https://community.appian.com/discussions/f/integrations/34900/boundary-in-multipart-form-data-to-http-request from last year!

Basis the thread in Appian the boundary is always 'TnQmfygKfP801A_kE1bGL-7YAFk_k6gl9'. So I don't think there is a way to set it to 'cpi' from within Appian. Please check with Appian Support if they can help with this! 

By the specification, the boundary can be any string. Expecting a specific value is not a good idea.

ChatGPT knows this:

In an HTTP `multipart/form-data` request, the boundary is a crucial component that separates different parts of the data being sent. Here are the key requirements and considerations regarding the boundary:

1. **Unique Boundary**: The boundary string must be unique within the content being sent. It should not appear in the actual data to avoid confusion in parsing.

2. **Format**: The boundary string must start with two hyphens (`--`). For example, if the boundary is `myBoundary`, it should be represented as `--myBoundary` at the beginning of each part.

3. **Content-Type Header**: The boundary must be specified in the `Content-Type` header of the request. The header should look like this:
```
Content-Type: multipart/form-data; boundary=myBoundary
```

4. **Length**: The boundary string should be reasonably short but long enough to ensure uniqueness. A common practice is to use a random string or a combination of characters that is unlikely to appear in the data.

5. **Termination**: The last boundary must be followed by an additional two hyphens to indicate the end of the multipart data. For example:
```
--myBoundary--
```

6. **Character Set**: The boundary string can include any ASCII characters except for control characters and the delimiter characters (such as space, tab, and the hyphen itself). It is common to use alphanumeric characters and some special characters.

7. **No Whitespace**: The boundary string should not contain any whitespace characters.

By adhering to these requirements, the multipart data can be correctly parsed by the server receiving the request.