Add Scope in Oracle Integration | SCOPE Action | INTEGRATION GENERATION 3

 In this article I have shared the steps to add scope action in Oracle Integration.

Knowledge:  👀 

SCOPE in Integration:

You can manage a group of Integratron Actions with a Scope action. The concept of scope is essential for designing complex integration flows, managing transactions, and controlling error handling.

• Error Handling: Each scope can have its own error handlers. If an error occurs within a specific scope, the associated error handler can be used to catch and handle the error.
• Integration Flow Design : Within an OIC integration, you can organize integration components (such as activities, branches, and error handlers) into different scopes. Each scope represents a distinct section of the integration flow.

Use case : Refer below image - let's add scope in an existing integration and later will put the adapter inside the scope.

Let's see the steps....

• Drag your cursor along the line below the trigger until the Add  icon appears. Search for SCOPE action, select SCOPE

• Click EDIT ICON 🖉 and then enter Scope Name "InvokeCalculatorServiceScope" (you can enter any meaningful name). Click ☑

• Click Save. Scope have been added successfully. 

Note: 🖉

If your requirement is just to know how to add a SCOPE, you can leave the below steps. You are done. You can close this article. 😁

• Now lets put the Invoke SOAP Connection & its Mapper inside the Scope. Click 𝩊 (rectangular icon) inside the Mapper, then select CUT ICON ✀ (Please refer below Image)

• Drag your cursor to SCOPE. Click on  𝩊 (rectangular icon) and then select PASTE, Click Into🡇

• Mapper moved successfully inside Scope. Now similarly lets move the Invoke inside the Scope.

• Move your cursor to Invoke Connection. Click 𝩊 (rectangular icon) then select CUT ICON ✀.  
• Now drag your cursor inside the SCOPE. Click on ➕ (plus icon), present below he mapper and then select PASTE.

(Please refer below image)

 

This way we have successfully added a SCOPE inside an existing integration flow and also have readjusted the flow by putting the scope connection & its mapper inside the SCOPE.

Note: 🖉

You may see a warning sign after putting the INVOKE Connection inside the SCOPE. This is because response of the INVOKE Connection moved inside the SCOPE which was earlier mapped with the Trigger Response, and you know that the elements defined in the parent scope have local visibility inside this scope. 

So, to fix this issue we need to declare a Variable in the integration which will store the INVOKE Response and can be accessed out of the SCOPE. The very same variable can be mapped with the Trigger.

If you want to implement this, you can follow NEXT ARTICLE.... 😇