A client application hardcodes all URIs for resource endpoints, allowing it to navigate the API without relying on server responses.

A client application receives resource representations that include hyperlinks to related resources, enabling dynamic navigation based on the server’s responses.

A client application receives a base URI from the server and constructs all subsequent resource URIs by concatenating strings.

A client application pre-fetches all possible resource states and transitions to minimize server interactions.

Select the Parallel Processing option and set the number of threads to the number of orders.

Select the Group By option and group the orders by the order number.

Select the Repeating Element field and map the source element that contains the orders.

Select the Sequential Processing option and set the batch size to the number of orders.

SOAP clients can easily hold stateful references to remote server-side SOAP objects.

SOAP is platform independent and programming language independent.

SOAP typically leverages XML-based payloads to communicate between two client machines across any modern network.

SOAP commonly serves as a cleaning agent that removes excess data from the transmissionprotocol.

SOAP provides flexibility for message formatting allowing for loose coupling between a client and a server.

SOAP over HTTP is typically not blocked by firewalls and proxy servers.

Unlimited

10

5

7

Supports asynchronous REST API invocations with callback URLs

Supports JSON, XML, binary, and URL-form-encoded payloads

Consumes REST APIs protected using OAuth Client Credentials

Supports WebSocket connections for real-time communication

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

Lookup values are retrieved from a back-end database at runtime.

Lookup values must include two or more domains associated with the corresponding SaaS applications.

A custom OIC XPath function is used to retrieve data from Lookups in the data mapper.

SOAP clients can easily hold stateful references to remote server-side SOAP objects.

SOAP is platform independent and programming language independent.

SOAP typically leverages XML-based payloads to communicate between two client machines across any modern network.

SOAP commonly serves as a cleaning agent that removes excess data from the transmission protocol.

SOAP provides flexibility for message formatting allowing for loose coupling between a client and a server.

SOAP over HTTP is typically not blocked by firewalls and proxy servers.

Stage File Action using a Read File in Segments operation

Stage File Action using a Write File operation

Switch Action

JavaScript Call Action

For Each Loop Action

Stage File Action using a Read File operation

You can create the new integration as a different major version of the existing one.

You can create the new integration from scratch by using the same display name and specifying a different identifier.

You can clone the existing integration and specify it to use the schedule pattern instead of the application pattern.

You can use the convert tool to change from the application pattern to the schedule pattern.

Create a connection between the two systems, then use a SQL query to access the Lookup table directly, and map the customer status codes.

Define a Lookup table containing the customer status code mappings, and then use the Invokeaction to call a web service for the transformation.

Design a custom script to perform the transformation, and then use the Lookup function within a Map action to reference the script and transform the customer status codes.

Create a Lookup table with the mappings of customer status codes, and then use the Lookup function within a Map action to reference the table and perform the transformation.