Both standard and custom HTTP headers can be defined for either the request or response.

File attachments can be accepted as a request option for the Trigger interface, but you cannot include attachments as a response to the client.

If you select a PUT or POST action (HTTP method), you must define a JSON response payload format.

Although you can define both query and template parameters, only template parameters will be available for mapping in the mapper because query parameters are considered optional.

You cannot clone an existing lookup if it is being currently referenced in one or more active OIC integrations

A custom OIC XPATH function must be used to retrieve data from a look up in the Data Mapper.

Lookup values are retrieved from a backend database at runtime

Lookup values must include two or more domains associated with corresponding Saas applications

Changes that are made to Lookups referenced in active integrations will take effect immediately without reactivating those integrations

The Read File in Segments operation allows for you to process the segments sequentially or in parallel.

You must provide the actual filename because file references cannot be processed by the Read File in Segments operation.

Segment sizes will default to 50 records but can be configured to any other segment size.

You will need to explicitly configure a Scope action for this operation if you want to add additional actions during the processing of each segment.