Editing BPMN (section)

=====End Events=====
* End Events signifies the end of a path in a process or subprocess. 
* End Events consume tokens.
* End Events are always throwing.
* there can be more than one End Event.
* a process instance lives until the last token arrived at an end event or a process terminating end event is reached. If the process is a Sub-Process it can be stopped prior through interrupting Intermediate Events. In this case the tokens are consumed by the Intermediate Event attached to the boundary.
* there six different end events:
** None/undefined
** message end event
** [[#Signal_End_Event|signal end event]]
** [[#Error_End_Event|error end event]]
** [[#Escalation_End_Event|escalation end event]]
** [[#Cancel_End_Event|cancel end event]]
** multiple consequences end event
** [[#Terminating_End_Event|terminating end event]]

======Signal End Event======
* for loose coupling (publisher subscribe)

======Error End Event======
* reaching in a process or subprocess immediately ends that process level, even if path are active
* the result can only be catched by an (nearest enclosing) intermediate error event attached to the subprocess boundary
* does not trigger compensation (different from Cancel End Event)

======Escalation End Event======
* like error end event, but process or subprocess is not aborted if there are still active path, so it triggers an additional activity

======Cancel End Event======
* another special end event, it's only used in transactional subprocess
* it interrupts the process or subprocess like the error end event

======Terminating End Event======
* ends the process level, even if there running paths
* doesn't propagate a result signal
* if it ends a subprocess, the next process level continues the normal flow