Invoking a callable flow from another flow in App Connect Enterprise as a Service
In this scenario, one flow that is running in App Connect Enterprise as a Service invokes (calls) another flow that is running in App Connect Enterprise as a Service.
Before you begin
About this task

Developing a callable flow
Procedure
To develop a callable flow in App Connect Enterprise as a Service, complete the following steps.
What to do next
You can test the behavior of your flow before you deploy it. Depending on your plan, you can either test with sample or real data. For more information, see Testing flows during development.
When your callable flow is complete, deploy it by following the appropriate instructions for your plan. .Deploying a callable flow (flow runs plan)
Procedure
If you're on the flow runs plan, deploy the callable flow in the following way.
- Go to the Manage
tab and click Deploy. - Select the callable flow, then click Next.
- Check the summary of the flow, then click
Deploy. A tile is added to the Manage page for your flow and is marked as
Inactive. - Open the tile menu
and click
Activate. The status on the tile changes toActiveand the deployed callable flow is ready to be called.
What to do next
Deploying a callable flow (VPC hours plan)
Before you begin
Callable flows use a private network connection to communicate with each
other. Therefore, when you deploy your callable flow, you must configure it to use a private network
connection. You can apply the default private network connection configuration
(default-switch-server-privatenetworkagent) when you create the integration runtime
or you can create your own private network connection before you deploy the flow. To create a
private network connection, expand Connect
in the navigation pane, click Private networks, then click
Create.
Procedure
If you're on the VPC hours plan, deploy the callable flow in the following way.
What to do next
Developing an invoking flow
Procedure
To create a flow in App Connect Enterprise as a Service that can invoke the callable flow, complete the following steps.
What to do next
Deploying an invoking flow
Procedure
- Deploying the flow on the flow runs plan
-
- Go to the Manage
tab and click Deploy. - Select the flow that contains the Invoke node, then click Next.
- Check the summary of the flow, then click Deploy.
A tile is added to the Manage page for your flow and is marked as
Inactive. - Open the tile menu
and click Activate.The status on the tile changes to
Activeand the deployed flow is ready to be triggered.
- Go to the Manage
- Deploying the flow on the VPC hours plan
-
- On the Manage page, go to the Integrations tab and click Deploy integration.
- Select the callable flow that contains the Invoke node, then click Next.
- Select an existing runtime, then click Next. Alternatively, create a runtime by clicking Create runtime. For more information, see Creating a runtime.
- On the Add configurations page, select a private network connection configuration, then click Next. You can select the default private network connection configuration default-switch-server-privatenetworkagent or you can select one that you created yourself.
- Check the summary of what you're deploying, then click Deploy.
A message indicates that the integration is being deployed. Refresh the browser to update the status. When the integration is deployed, a tile is shown on the Integrations tab of the Manage page and the status is Active. The invoking flow is ready to be triggered.
Results
After both the invoking and callable flows are deployed, when the invoking flow is triggered, the Callable flow Invoke node invokes the Callable Input node of the callable flow. The callable flow runs and the Callable flow Reply node returns data to the Callable flow Invoke node. Subsequent nodes in the flow can then use this returned data.
Your callable flows are listed on the Callable flows page (in the
Connect category
of the navigation pane). The table
lists the applications and endpoints for the callable flows that you're connected to. You can also
see whether the callable flow is provided by App Connect or by an on-premises integration server.

.