Process Developer > Part II: Creating and Modifying Processes > Gateways and Control Flow > Fork Join
  

Fork Join

The notation for a fork join container is BPMN only. This control flow is equivalent to a BPEL Flow activity.
When you drag a fork join to the canvas, it contains two paths by default. You can add additional paths as needed. Each path contains one or more activities. Each path executes in parallel.
Required Properties
Optional Properties
none
Name. See Selecting Activity Labels
Join Condition. See Creating a Join Condition for an Incoming Link
Suppress Join Failure. See Process Element and Properties
Comment. See Adding Comments to a Process
Documentation. See Adding Documentation to a Process
Setting Visual Properties and Using Your Own Library of Images
Execution State. See Viewing the Execution State of an Activity or Link
Extension Attributes and Extension Elements. See Declaring Extension Elements and Attributes.
To build a Fork Join:
  1. 1. From the Control Flow palette, drag a fork join to the Process Editor canvas.
  2. 2. Drag an activity, such as Receive task, to one path.
  3. 3. Continue dragging the other activities to the same or other path.
  4. 4. Add a new path by right mouse clicking the Fork Join and selecting Add Path.
The following illustration shows an example of a Fork Join activity containing two invokes executing in parallel.