While tasks represent what needs to be done to achieve the goal of a process, events describe asynchronous interactions between the process and the external world.
Events are in
How to recognize events? While writing, you should follow this rule to help BPMN Sketch Miner distinguish them from tasks.
Events are represented within
( ) in BPMN Sketch Miner.
This is the closest shape to the circular elements of BPMN you can actually type.
event label is written between the round parenthesis
By default, untyped events are shown as intermediate events.
Depending on the event type, the first event of a sequence may become a start event and the last event of a sequence may become its end event.
Start and End Events
Start events represent the beginning of the process execution and describe when a process should start. End events are reached when processes finish their execution.
By default, BPMN Sketch Miner automatically adds start and end event to each sequence of tasks.
To describe them in more detail, just mention them explicitly in the text at the beginning or at the end of each sequence of tasks using the
Timer events represent literally when (which date, at what time, how often) a process will start.
Timer events can also be found within a process. In this case they are used to explicitly represent a delay in the process execution.
Error events indicate that a process failed.
Message events represent interactions with exactly one external communication party. From the perspective of the process, messages can be sent (black envelope symbol) or received (white envelope symbol).
A process starts when a message is received.
A process completes after a message has been sent.
After a message has been sent, a process waits until a reply message is received.
Note that a process cannot start by sending a message or end by receiving one. This is why - when listed in this order - the two events are kept as intermediate events.
Signal events also represent an external interaction, which unlike messages may involve multiple parties (as in broadcast or multicast communication).
We use the terms
publish to indicate throwing a signal and
notify to indicate catching the arrival of the signal and the corresponding notification of the process.
A new process instance is triggered by a signal.
A process completes by broadcasting a signal.
After a signal has been broadcast, the process waits for the notification of another signal.
Escalation events identifies a business situation that a process might need to react to.
This process does not normally complete, instead it requires to escalate processing elsewhere.
Unlike an error, an escalation event is non critical. Process execution can continue and still reach a successful conclusion.
Terminate events stop the execution of the process, even if other parallel execution branches may not have been yet finished.
If task A finishes first, the process will wait for B to finish. However as soon as B is complete, the process will end (even if A is still running).