How to use the Dynamic Invoke feature in OIC.
Local Integration feature enables user to invoke an active child flow or collocated flow. User created another child flow. Assume that the interface or service definition has not changed between old and new child flow. This feature enables parent flow to dynamically invoke the new child flow with minimal change and without loosing any mappings.
This blog explains this new feature with a simple example.
Example : User has configured the parent flow to invoke the Child 1 using Local invoke. But at Runtime Child2 flow is invoked dynamically.
Step By Step Guide:
- Create a Child 1 flow with Trigger as Rest and then activate the flow.
a. Create a flow with App Driven Orchestration.
b. Provide all the necessary details and click on Create.
c. Select the Trigger as Sample Rest EndPoint.
d. Provide all the necessary details and click on Next.
e. Specify the necessary information and click on Next.
f. On Summary page click on Done.
g. Activate the Child1 flow or import the Child1 flow and activate.
IAR file for CHILD 1.
2. Create another Child2 flow with Trigger as Rest and then activate the flow.
Follow the same steps mentioned for Child1 to create the Child2 flow or use the attached Child2 flow.
IAR file for CHILD 2.
3. Create a Parent flow and modelled the Child1 flow and then activate the parent flow.
a. Create a flow with App Driven Orchestration.
b. Provide all the necessary details and click on Create.
c. Select Sample Rest End Point connection as Trigger.
d. Provide the necessary information and click on Next.
e. You can specify the query parameters and click on Next.
f. Specify the necessary information and click on Next.
g. On Summary page click on Done.
h. Drag and drop the integration and configure it.
i. Select the integration childone and click on next.
j. Select the operation and click on Next
k. On Summary page click on Done.
l. Now configure the map by clicking on it.
k. Activate the parent flow .
IAR file for PARENT FLOW.
4. Now any child flow can be invoked by replacing the the code and version of that child flow in the endpoint below.
Here parent flow is modelled with only child flow1 but it can also invoke the child flow2 by providing the code and version.
Limitations :
- The new feature is supported only for Rest type child flow i.e. dynamic invoke of soap type and schedule type child flow is not supported.
- The interface should not change between then child flows. If the child interface changes independently then parent may face runtime error.
- Child flow can be a new integration or cloned from existing or a newer version of existing flow.
