Start and End Events (BPMN Descriptive)

To create a start, click the Start tool to select it, and then click in the diagram.

Note A start event is created by default when you create a pool (see Pools and Lanes (BPMN Descriptive)).

By default, a standard start is created. To change the type of the start, select it, click the Properties tool, and select the appropriate type. In BPMN 2.0 Descriptive, PowerDesigner supports the following types of start events:

Symbol	Description
	Undefined Start Event - The process simply starts without any specific triggering event.
	Message Start Event - The process begins following receipt of a message, such as an order or enquiry.
	Timer Start Event - The process begins on a specific date or at a specific time, such as Monday morning at 9am.

To create an end:

Select an object in the diagram and click (or click and drag) the End tool in its context toolbar to create a new end after it in the control flow, or
Click the End tool in the bottom toolbar and then click in the diagram.

By default, a standard end is created. To change the type of end, click the Properties tool and select a type from the list. In BPMN 2.0 Descriptive, PowerDesigner supports the following types of ends:

Symbol	Description
	Standard End Event - The process simply ends when all of the tasks are completed.
	Message End Event - The process terminates by sending a message, such as a quotation, invoice, or report.
	Terminate End Event - All tasks in any parallel sequence flows are terminated immediately when one branch reaches a terminate end event.

Starts and ends can have the following properties:

Property	Description
Name/Code/Comment	Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.

Property

Description

Name/Code/Comment

Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.