Version: latest

None events

None events are unspecified events, also called ‘blank’ events.

workflow

None start events#

A workflow can have at most one none start event (besides other types of start events).

A none start event is where the workflow instance or a subprocess starts when the workflow or the subprocess is activated.

None end events#

A workflow or subprocess can have multiple none end events. When a none end event is entered then the current execution path ends. If the workflow instance or subprocess has no more active execution paths then it is completed.

If an activity has no outgoing sequence flow then it behaves the same as it would be connected to a none end event. When the activity is completed then the current execution path ends.

Additional resources#

XML representation

A none start event:

<bpmn:startEvent id="order-placed" name="Order Placed" />

A none end event:

<bpmn:endEvent id="order-delivered" name="Order Delivered" />

Using the BPMN modeler

Adding a none start event:

start-event

Adding a none end event:

end-event

Workflow lifecycle

Workflow instance records of a none start event:

Intent	Element Id	Element Type
ELEMENT_ACTIVATING	order-placed	START_EVENT
ELEMENT_ACTIVATED	order-placed	START_EVENT
ELEMENT_COMPLETING	order-placed	START_EVENT
ELEMENT_COMPLETED	order-placed	START_EVENT

Workflow instance records of a none end event:

Intent	Element Id	Element Type
ELEMENT_ACTIVATING	order-delivered	END_EVENT
ELEMENT_ACTIVATED	order-delivered	END_EVENT
ELEMENT_COMPLETING	order-delivered	END_EVENT
ELEMENT_COMPLETED	order-delivered	END_EVENT