The Integration blog covers the latest in product updates, best practices, customer stories, and more.

What are Embeddable Oracle Integration Cloud Process Components and why are they important?

Tom Albrecht
Product Manager and Developer

To get their job done, today’s knowledge worker is often forced to use many different application user interfaces.  For example, they may be using Oracle Sales Cloud to review their Sales Opportunities, and then have to navigate to a completely different application UI (with a different look and feel) to approve some other sales related tasks. Why not consolidate this experience and give the knowledge worker the experience of performing their work in the context of where they spend most of their time?

The purpose of this Blog is to describe how this can be accomplished by demonstrating how Oracle Integration Cloud (OIC) Process Components can be embedded inside of an external application so that the knowledge worker can stay within the context of the main application where they perform their work.

Process Cloud delivers a set of embeddable components.   These components include Start Form, Task Detail, Task List, History Component, and many others. These components can be found on your OIC Server at the following URL:  https://<oic-server>/ic/pub/components/

See Process UI Components Available for Embedding for a list of all the components and see Experimenting with Process UI Components for instructions on how to use the Embeddable Components Cookbook UI.

There are two ways in which Process Components can be embedded:

  • Simple URL
  • Embeddable Javascript Component

Let’s look at both of these options.

Simple URL

The Simple URL method is much easier/quicker to use and provides slightly less functionality than embedding the javascript component but allows embedding in external applications that do not allow consumption of javascript.

To use the Simple URL method to load a Process Start Form,  you can place the below URL within the external application:

https://<oic-server>/ic/pub/components/pages/startform.html?&startformData={"processDefId":"oracleinternalpcs~Product_Request!1.0~Process", "serviceName":"Process.service","operation":"start","startType":"START_PCS_FORM"}&payload={"opportunityId":"' + OptyId + '"}

The above example is a Sales Cloud example where the Product Request start form will be loaded and the opportunityId is passed from the Sales Cloud UI to the start form.  The below screenshot shows the Product Request Form embedded inside Sales Cloud.

To use the Simple URL method to embed the Process Task List, you can place the below URL within the external application:


In both cases, query parameters can be passed on the HTML query string to provide configuration options.  See Experimenting with Process UI Components for more information on parameters that can be set.  The same options that are available to be set on the individual components can be set as Query parameters on the URL.   After logging into the Cookbook, select the Cookbook tab, then select the Component you are using on the left menu, and then observe the options under the Component Setup panel.

Embeddable Javascript Component

The second method that can be used is to embed the actual javascript component within your external application.  This provides more configurability than the simple URL as you will have more control over styling as well as handling events from the components such as ‘Form Submission’.

For example, the screenshot below shows a Process Start form embedded inside of an Oracle Content and Experience Cloud Site.  Notice that the Process Start Form has been styled to match the Site.

For a quick summary video how to embed the Javascript component, please see the following link: Embedding Process Components using the Javascript Library.

For detailed documentation on embedding the Javascript component, please see the official documentation link at: Embedding Process UI Components in Other Applications.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.