Capturing SAAS customization's in Oracle Integration
In this blog, we are looking at one of the powerful features of adapters in Oracle Integration Cloud(OIC).
Let us say, I have built an integration between Oracle Engagement Cloud (OEC) (formerly known as Oracle Sales Cloud) and NetSuite (i.e., Opportunity to Sales Order). After completion of an integration, there could be some customization's in OEC like creation of custom object, custom fields etc which we need to capture as part of the integration flow. How can we capture it? Do we need to re-implement the complete integration flow? No. With just few clicks, you can capture the customization's of SAAS application in OIC.
Let us see how we can capture the SAAS customization's in OIC.
In this blog, am also talking about how to create custom field in OEC so that we can see complete end-end flow and then we shall look into how to capture SAAS custom field(s) in OIC without re implementing the complete integration.
Steps to create custom field in OEC:
Login to OEC
Click on Username drop down, click on Manage Sandboxes
Create new sandbox and activate it.
Click on Navigator --> Click on Application Composer
Expand Standard Objects and Expand Opportunity and Create a Custom Field ‘NSSalesOrderID’ to hold the Sales Order ID after creating Sales order in NetSuite application.
Now, you can show this custom field in Update Opportunity page by editing Details Page Layouts
Go back to Manage Sandboxes and publish the sandbox to reflect the customizations on the base (mainline) application.
You can go to Simplified UI of OEC, click on Sales and Click on Opportunity and Edit one of the existing opportunity to verify your custom field
Go back to Application Composer, Click on Import and Export and click on Generate button which will generate the artifacts required (like web services, file import and export options) for custom fields and custom objects.
Steps to capture custom field in OIC:
Go to the Integrations and then click on Connections
Locate the connection to refresh
From the menu at the right, select Refresh Metadata. And a message is displayed indicating that the refresh was successful
Click on Integrations and Edit the required Integration Flow
Select UpdateOpty activity and Click on More Actions and Click on “Regenerate”
Click on Mappings activity to verify the custom field (NSSalesOrderID_c) which is created.
Please note that _c represents custom field in Oracle Engagement Cloud. In OEC, _c will be appended by default for the API name when you create it.
You can do the appropriate mapping to the custom field to capture the data.
With just two clicks i.e., Refresh Metadata and Regenerate options, you could see the custom fields and custom objects in Oracle Integration without re-implementing the complete integration flow. This is the beauty of Oracle Integration Cloud.