Fork Join

ActiveVOS Designer User’s Guide

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 and optional properties for Fork Join
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 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 Elements. See Declaring Extension Elements and Attributes.

To build a fork join:

From the Control Flow palette, drag a fork join to the Process Editor canvas.
Drag an activity, such as receive task, to one path.
Continue dragging the other activities to the same or other path.
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.

fork join activity with 2 invokes