Try OpenEdge Now
skip to main content
Developing BPM Applications with Developer Studio
Getting started with Progress Developer Studio for OpenEdge : Exploring Progress OpenEdge BPM Designer : Using the Tasks pane : Using shapes
Using shapes
The table below provides information about the Shapes listed when you click the Draw Shapes link in the Tasks pane. These shapes follow standard Business Process Modeling Notation (BPMN) and include Activities (represented by a rounded rectangle); event objects such as Start or End (represented by a circle); and Gateways (represented by a diamond) that indicate a change in the workflow, such as the joining, merging, splitting, or deciding of the flow’s direction.
Table 10. Shapes in Tasks Pane
An event object that specifies the beginning of a business process. Each process must have only one Start workstep.
This activity represents the basic unit of work that you can assign to one of the following performer types: User (a valid human performer or group), Adapter, or Subprocess.
This gateway represents a decision point in the process flow. If the specified condition is not met, the default branch is taken.
Exclusive Or-Join
This gateway enables the process flow to proceed only once from multiple previous worksteps to a next workstep, and terminates any other human-performed previous worksteps. This shape is not available for Web Applications.
This gateway connects multiple predecessor worksteps and one successor workstep. The successor workstep is performed if any of the predecessor worksteps have been completed.
This gateway can act as an And Join or as a Split (or And-Fork). When it connects multiple predecessor worksteps to a single successor workstep, it acts as an And-Join. When it connects one predecessor workstep to multiple successor worksteps, it acts as a Split (or And-Fork). The successor worksteps are performed in parallel and only if the predecessor was completed. This enables you to synchronize the completion of multiple predecessor worksteps. This shape (gateway) is not available for Web applications.
An intermediate workstep in a process, indicating that the workstep is waiting for a message or will send a message when it is activated. Messages can also be assigned to the Start or End of a process.
An event object that signifies that the application has come to a normal end. You can add multiple End worksteps in a process.