Table of Contents

Search

  1. Preface
  2. Part 1: Using Process Developer
  3. Part 2: Creating and Modifying Processes
  4. Part 3: Functions, Events, Errors, and Correlation
  5. Part 4: Testing and Deployment
  6. Part 5: Process Central and Process Server (On-Premises)

Process Developer

Process Developer

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
Suppress Join Failure. See Process Properties
Extension Attributes and Extension Elements. See Declaring Extension Elements and Attributes.
To build a Fork Join:
  1. From the
    Control Flow
    palette, drag a
    fork join
    to the Process Editor canvas.
  2. Drag an activity, such as Receive task, to one path.
  3. Continue dragging the other activities to the same or other path.
  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.

0 COMMENTS

We’d like to hear from you!