Editing BPMN (section)

=====Intermediate Events=====
* Intermediate can be split in catching und sending/throwing. 
* Catching/receiving intermediate events are waiting until the event arrives, throwing events are throwing and continuing
* there are no throwing timer events, just catching
* Intermediate events at an activity borders are catching events, listening for the trigger and called '''boundary events'''. They can be located anywhere at the border.
* boundary events can be '''interrupting''' (solid line) or '''non-interrupting''' (dashed line). The interrupting event stops the activity immediately, including running [[#Event_Sub-Process|Event Sub-Processes]]
** Error, Compensation and Cancel Event are always interrupting (non-interrupting make no sense)
** Compensation is only called, if activity is completed
* boundary events are listening as long the activity is running
* None intermediate events can e.g. be used to model state transitions of objects
* there are 12 intermediate events:
** [[#None_Intermediate_Event|None/undefined Intermediate Event]]
** [[#Message_Intermediate_Event|Message Intermediate Event]]
** [[#Timer_Intermediate_Event|Timer Intermediate Event]]
** rule/condition
** [[#Error_Intermediate_Event|Error Intermediate Event]]
** [[#Signal_Intermediate_Event|Signal Intermediate Event]]
** [[#Link_Intermediate_Event|Link Intermediate Event]]
** [[#Compensation_Intermediate_Event|Compensating Intermediate Event]]
** [[#Escalation_Intermediate_Event|Escalation Intermediate Event]]
** [[#Cancel_Intermediate_Event|Cancel Intermediate Event]]
** [[#Multiple_Intermediate_Event|Multiple Intermediate Event]]
** [[#Parallel_Intermediate_Event|Parallel Intermediate Event]]

======None Intermediate Event======
* is used as a throwing event to model some state changes of the process
* not allowed on a boundary

======Message Intermediate Event======

======Timer Intermediate Event======
* at boundary in can be a stop-watch which starts when the activity starts or a alarm at a specific date/time

======Error Intermediate Event======
* there is a throwing and catching Error Intermediate Event
* Catching Error Intermediate Event is only for boundary and always interrupting, in case of multi-instances all instances are interrupted
* in case of boundary catching the Sub-Process was cancelled and the data is not available and potentially lost. This could be solved by an catching [[#Event_Sub-Process|Event Sub-Process]] Start Event.

======Signal Intermediate Event======
* a Signal is an undirected message

======Link Intermediate Event======
* conncecting sequence flow on different pages via a link id

======Compensation Intermediate Event======
* By default, the compensation throwing Event waits for the completion of the triggered compensation handler. Alternatively, compensation can just be triggered without waiting for its completion, by setting the throw Compensation Event’s waitForCompletion attribute to false
* Compensation handlers are associated to an Activity by a boundary catching Compensation Event. The handler can be triggered later in the process flow and is only executed if the Activity is completed successfully (other boundary event can only be triggered if the Activity is active and not completed).
* Triggered Compensation only refer to the own Process/Pool.

======Escalation Intermediate Event======
* meant for escalating to a higher level of responsibilities

======Cancel Intermediate Event======
* must be attached to a boundary of a Transaction Sub-Process
* will direct the flow after the Transaction has been rolled back and all compensation has been completed

======Multiple Intermediate Event======
* Catching if one of many events
* Throws all events

======Parallel Intermediate Event======
* no throwing, only catching
* all Events have to be there, to trigger the catch