BPMN events

Events can occur with different continuations, at different locations and with different types.

Table of contents

1.0 Event continuations, that are defined by BPMN are:

  • interrupting
  • non-interrupting

Any event continuation can be combined with any event location, except non-interrupting and end.

2.0 Event locations, that are defined by BPMN are:

  • start
  • intermediate
  • end
No. JSON request / definition JSON request / shape Graphic display BPMN definition BPMN display
1 interrupting:
"properties": {
  "type": "evStart",
  "kind": "OBJ"
}
non-interrupting:
"properties": {
  "type": "evStartNonInterrupting",
  "kind": "OBJ"
}
interrupting:
"properties": {
  "type": "evStart"
}
non-interrupting:
"properties": {
  "type": "evStartNonInterrupting"
}
interrupting:
GRAPHIC-eventStart
non-interrupting:
GRAPHIC-eventStartNonInterrupting
interrupting:
<startEvent> ... </startEvent>

non-interrupting:
<startEvent isInterrupting="false"> ... </startEvent>
interrupting:
GRAPHIC-eventStart
non-interrupting:
BPMN-eventStartNonInterrupting
2 interrupting:
"properties": {
  "type": "evIntermediate",
  "kind": "OBJ"
}
non-interrupting:
"properties": {
  "type": "evIntermediate-
NonInterrupting",
  "kind": "OBJ"
}
interrupting:
"properties": {
  "type": "evIntermediate"
}

non-interrupting:
"properties": {
  "type": "evIntermediate-
NonInterrupting"
}
interrupting:
GRAPHIC-eventIntermediate
non-interrupting:
GRAPHIC-eventIntermediateNonInterrupting
interrupting:
<intermediate-
ThrowEvent> ... </intermediate-
ThrowEvent>

non-interrupting:
<intermediate-
ThrowEvent isInterrupting="false"> ... </intermediate-
ThrowEvent>
interrupting:
BPMN-eventIntermediate
non-interrupting:
BPMN-eventIntermediateNonInterrupting
3 interrupting:
"properties": {
  "type": "evEnd",
  "kind": "OBJ"
}
interrupting:
"properties": {
  "type": "evEnd",
}
interrupting:
GRAPHIC-eventEnd
interrupting:
<endEvent> ... </endEvent>
interrupting:
BPMN-eventEnd

3.0 Event types, that are defined by BPMN are:

  • GRAPHIC-event_none none
    This event does not have a defined trigger .
  • GRAPHIC-event_throwMessage throw message; add "evType": "throwMessage" to "properties" within the Request JSON
    A message is sent to a participant when the event has been triggered.
  • GRAPHIC-event_catchMessage catch message; add "evType": "message" (for start events) or "evType": "catchMessage" (for intermediate events) to "properties" within the Request JSON
    A message arrives from a participant and triggers the event.
  • GRAPHIC-event_timer timer; add "evType": "timer" (for start events) or "evType": "catchTimer" (for intermediate events) to "properties" within the Request JSON
    A specific date-time or a specific cycle count triggers the event.
  • GRAPHIC-event_throwError throw error; add "evType": "throwError" to "properties" within the Request JSON
    An error is generatedand when the event has been triggered.
  • GRAPHIC-event_catchError catch error; add "evType": "catchError" to "properties" within the Request JSON
    The execution of a business activity creates an error and triggers the event.
  • GRAPHIC-event_throwEscalation throw escalation; add "evType": "escalation" (for end events) or "evType": "throwEscalation" (for intermediate events) to "properties" within the Request JSON
    An escalation is generatedand when the event has been triggered.
  • GRAPHIC-event_catchEscalation catch escalation; add "evType": "escalation" (for start events) or "evType": "catchEscalation" (for intermediate events) to "properties" within the Request JSON
    A specified restriction on the execution of a business activity cannot be complied with and triggers the event.
  • GRAPHIC-event_throwCancel throw cancel; add "evType": "throwCancel" to "properties" within the Request JSON
    An transaction has to be canceled when the event has been triggered.
  • GRAPHIC-event_catchCancel catch cancel; add "evType": "catchCancel" to "properties" within the Request JSON
    A transaction cannot be completed and triggers the event.
  • GRAPHIC-event_throwCompensation throw compensation; add "evType": "throwCompensation" to "properties" within the Request JSON
    A compensation is necessary when the event has been triggered.
  • GRAPHIC-event_catchCompensation catch compensation; add "evType": "catchCompensation" to "properties" within the Request JSON
    A compensation occurs and triggers the event.
  • GRAPHIC-event_conditional conditional; add "evType": "conditional" to "properties" within the Request JSON
    A condition becomes true and triggers the event.
  • GRAPHIC-event_throwLink throw link; add "evType": "throwLink" to "properties" owithin the Request JSON
    The connection to another section of the same business process (e.g. loop start or sequence shortcut start) needs to be initiated when the event has been triggered.
  • GRAPHIC-event_catchLink catch link; add "evType": "catchLink" to "properties" within the Request JSON
    A connection to another section of the same business process is to be closed (e.g. loop end or sequence shortcut end) and triggers the event.
  • GRAPHIC-event_throwSignal throw signal; add "evType": "signal" (for end events) or "evType": "throwSignal" (for intermediate events) to "properties" within the Request JSON
    A signal to another business process needs to be broadcast when the event has been triggered.
  • GRAPHIC-event_catchSignal catch signal; add "evType": "signal" (for start events) or "evType": "catchSignal" (for intermediate events) to "properties" within the Request JSON
    A signal arrives that has been broadcast from another business process and triggers the event.
  • GRAPHIC-event_terminate terminate; add "evType": "terminate" to "properties" within the Request JSON
    All activities in the business process should be ended immediately when the event has been triggered.
  • GRAPHIC-event_throwMultiple throw multiple; add "evType": "multiple" (for end events) or "evType": "throwMultiple" (for intermediate events) to "properties" within the Request JSON
    All of multiple consequences (trigers) occure when the event has been triggered.
  • GRAPHIC-event_catchMultiple catch multiple; add "evType": "multiple" (for start events) or "evType": "catchMultiple" (for intermediate events) to "properties" within the Request JSON
    At least one of several consequences (trigers) has been encountered and triggers the event.
  • GRAPHIC-event_parallelMultiple parallel multiple; add "evType": "parMultiple" (for start and end events) to "properties" within the Request JSON
    All of several triggers have been encountered and trigger the event.

4.0 All available combinations of event continuations, locations and types:

BPMN-eventCombinations