Parallel flows can be achieved using the Flow and FlowN (ForEach in BPEL 2.0) activities. Flow activity will help to execute the BPEL activities in parallel. This will reduce the process time if independent activities are performed as a part of the same business process. Flow activity is typically used in scenarios where results from invoking multiple asynchronous processes are independent to each other. Flow activity will determine the number of flow arms during design time. Flow allows calling or executing different business logic simultaneously, but the order of execution is not guaranteed. FlowN allows true parallelism by calling upon the same set of business logic on different sets of data. The ForEach construct, introduced in BPEL 2.0, also allows the process to dynamically pick up partners and perform operations similar to FlowN.
The following image shows the Flow activity:
A code snippet showing the flow activity is as follows:
<flow name...