Event-based Gateway - Revision history

Admin at 13:00, 3 May 2017

2017-05-03T13:00:28Z

Admin at 12:32, 30 September 2015

2015-09-30T12:32:29Z

Admin at 07:43, 18 September 2015

2015-09-18T07:43:35Z

Admin: Created page with "{{DISPLAYTITLE:Event-based Gateway}} Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Event-based_Gateway-01.png === Description === The Event-Based Gateway r..."

2015-09-17T14:16:53Z

Created page with "{{DISPLAYTITLE:Event-based Gateway}} Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Event-based_Gateway-01.png === Description === The Event-Based Gateway r..."

New page

{{DISPLAYTITLE:Event-based Gateway}}
[[Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Event-based_Gateway-01.png]]

=== Description ===

The Event-Based Gateway represents a branching point in the Process where the alternative paths that follow the Gateway are based on Events that occur, rather than the evaluation of Expressions using Process data (as with an Exclusive or Inclusive Gateway). A specific Event, usually the receipt of a Message, determines the path that will be taken. Basically, the decision is made by another Participant, based on data that is not visible to Process, thus, requiring the use of the Event-Based Gateway.

For example, if a company is waiting for a response from a customer they will perform one set of Activities if the customer responds “Yes” and another set of Activities if the customer responds “No.” The customer’s response determines which path is taken. The identity of the Message determines which path is taken. That is, the "Yes" Message and the "No" Message are different Messages—i.e., they are not the same Message with different values within a property of the Message. The receipt of the Message can be modeled with an Intermediate Event with a Message trigger or a Receive Task. In addition to Messages, other triggers for Intermediate Events can be used, such as Timers.

=== Layer ===
[[la_layer::Layers:Business Process Sub-layer | Business Process Sub-layer]]

=== Object Class ===
[[la_class::Objects:X-BPMN Notations | X-BPMN Notations]]

=== Object Category ===
[[la_category::Gateways]]

=== Reference Content ===
*Business Process Reference Content
*Performance Model Reference Content
*Measurement Reference Content
*Process Architecture Reference Content
*IT Process Map Reference Content

[[la_position::11| ]]
[[la_pgrel::pg-xbpmn| ]]

@@ Line 14: / Line 14: @@
 *Re-engineering Reference Content
 *Transformation Benchmarking Reference Content
-*Innovation Reference Content
+*Innovation Reference Content[[Category:Objects Inner]]

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:Event-based Gateway}}
+{{DISPLAYTITLE:Event-based Gateway}}{{#lead-mw-content: XbpmnNotations|getPageContent|{{FULLPAGENAME}} }}
-[[Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Event-based_Gateway-01.png]]
-−
-=== Description ===
-−
-The Event-Based Gateway represents a branching point in the Process where the alternative paths that follow the Gateway are based on Events that occur, rather than the evaluation of Expressions using Process data (as with an Exclusive or Inclusive Gateway). A specific Event, usually the receipt of a Message, determines the path that will be taken. Basically, the decision is made by another Participant, based on data that is not visible to Process, thus, requiring the use of the Event-Based Gateway.
-−
-For example, if a company is waiting for a response from a customer they will perform one set of Activities if the customer responds “Yes” and another set of Activities if the customer responds “No.” The customer’s response determines which path is taken. The identity of the Message determines which path is taken. That is, the "Yes" Message and the "No" Message are different Messages—i.e., they are not the same Message with different values within a property of the Message. The receipt of the Message can be modeled with an Intermediate Event with a Message trigger or a Receive Task. In addition to Messages, other triggers for Intermediate Events can be used, such as Timers.
-−
-=== Layer ===
-[[la_layer::Layers:Business Process Sub-layer | Business Process Sub-layer]]
-−
-=== Object Class ===
-[[la_class::Objects:X-BPMN Notations | X-BPMN Notations]]
-−
-=== Object Category ===
-[[la_category::Gateways]]
 === Reference Content ===
@@ Line 30: / Line 14: @@
 *Re-engineering Reference Content
 *Transformation Benchmarking Reference Content
 *Innovation Reference Content
-−
-[[la_position::11| ]]
-[[la_pgrel::pg-xbpmn| ]]

@@ Line 23: / Line 23: @@
 *Process Architecture Reference Content
 *IT Process Map Reference Content
 [[la_position::11| ]]
 [[la_pgrel::pg-xbpmn| ]]