Using shapes

Table 8 provides information about the Shapes listed when you click the Draw Shapes link in the Tasks pane. These shapes follow standard BPMN notation 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 8. Shapes in Business Process Modeler Tasks Pane
Shape	Represents	Description
	Start	An event object that specifies the beginning of a business process. The default name is Start. Each Business Process Modeler process must have exactly one Start workstep.
	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 of performers), Adapter, or Subprocess.
	Decision	This gateway represents a decision point in the process flow. If the specified condition is not met, then the default branch is taken.
	Exclusive Or-join	This gateway allows the process flow to proceed only once from multiple predecessor worksteps to a successor workstep, and terminates any other human-performed predecessor worksteps. This shape is not available for Web applications.
	Or-join	This gateway connects multiple predecessor worksteps and one successor workstep. The successor workstep is performed if any of the predecessor worksteps have been completed.
	And Gateway	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 an And-Fork). The successor worksteps are performed in parallel and only if the predecessor workstep was completed. This enables you to synchronize the completion of multiple predecessor worksteps. This gateway is not available for Web applications.
	Message	An intermediate workstep in a process, indicating that the workstep is waiting for a message or is used to send a message when it is activated. Message worksteps are used for notational purposes only in Business Process Modeler.
	End	An event object that specifies that the application has come to a normal end. Business Process Modeler allows multiple End worksteps.