BPMN events

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

Table of contents

• 1.0 - Event continuations
• 2.0 - Event locations
• 3.0 - Event types
• 4.0 - All available combinations of event continuations, locations and types

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: non-interrupting:	interrupting: <startEvent> ... </startEvent> non-interrupting: <startEvent isInterrupting="false"> ... </startEvent>	interrupting: non-interrupting:
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: non-interrupting:	interrupting: <intermediate- ThrowEvent> ... </intermediate- ThrowEvent> non-interrupting: <intermediate- ThrowEvent isInterrupting="false"> ... </intermediate- ThrowEvent>	interrupting: non-interrupting:
3	interrupting: "properties": {   "type": "evEnd",   "kind": "OBJ" }	interrupting: "properties": {   "type": "evEnd", }	interrupting:	interrupting: <endEvent> ... </endEvent>	interrupting:

3.0 Event types, that are defined by BPMN are:

• none
  This event does not have a defined trigger.
• throw message; add "evType": "throwMessage" to "properties" within the Request JSON
  A message is sent to a participant when the event has been triggered.
• 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.
• 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.
• throw error; add "evType": "throwError" to "properties" within the Request JSON
  An error is generatedand when the event has been triggered.
• catch error; add "evType": "catchError" to "properties" within the Request JSON
  The execution of a business activity creates an error and triggers the event.
• 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.
• 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.
• throw cancel; add "evType": "throwCancel" to "properties" within the Request JSON
  An transaction has to be canceled when the event has been triggered.
• catch cancel; add "evType": "catchCancel" to "properties" within the Request JSON
  A transaction cannot be completed and triggers the event.
• throw compensation; add "evType": "throwCompensation" to "properties" within the Request JSON
  A compensation is necessary when the event has been triggered.
• catch compensation; add "evType": "catchCompensation" to "properties" within the Request JSON
  A compensation occurs and triggers the event.
• conditional; add "evType": "conditional" to "properties" within the Request JSON
  A condition becomes true and triggers the event.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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.
• 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: