Inclusive Gateway - Revision history

Admin at 13:00, 3 May 2017

2017-05-03T13:00:30Z

Admin at 12:32, 30 September 2015

2015-09-30T12:32:54Z

Admin at 07:43, 18 September 2015

2015-09-18T07:43:53Z

Admin: Created page with "{{DISPLAYTITLE:Inclusive Gateway}} Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Inclusive_Gateway-01.png === Description === Inclusive Gateways are used f..."

2015-09-17T14:19:50Z

Created page with "{{DISPLAYTITLE:Inclusive Gateway}} Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Inclusive_Gateway-01.png === Description === Inclusive Gateways are used f..."

New page

{{DISPLAYTITLE:Inclusive Gateway}}
[[Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Inclusive_Gateway-01.png]]

=== Description ===

Inclusive Gateways are used for modeling points of synchronization of a number of branches, not all of which are active, after which one or more alternative branches are chosen within a Choreography flow. For example, one of more branches MAY be activated upstream, in parallel, depending on the nature of goods in an order (e.g., large orders, fragile goods orders, orders belonging to pre-existing shipment contracts), and these are subsequently merged. The point of merge results in one or more risk mitigating outcomes (e.g., special insurance protection needed, special packaging needed, and different container categories needed). Inclusive Gateways are also used within an Orchestration Process see page 292.

Like Exclusive Gateways, Inclusive Gateways are used in a Choreography, but they are constrained by the lack of a central mechanism to store the data that will be used in the Condition expressions of the Gateway’s outgoing Sequence Flows. Choreographies MAY contain natural language descriptions of the Gateway’s Conditions to document the one more alternative paths of the Choreography (e.g., “special insurance protection needed,” “special packaging needed,” and different “container category needed”), but such Choreographies would be underspecified and would not be enforceable. To create an enforceable Choreography, the Gateway Conditions MUST be formal Condition Expressions. In general the following rules apply for the Expressions.

=== 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::12| ]]
[[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:Inclusive Gateway}}
+{{DISPLAYTITLE:Inclusive Gateway}}{{#lead-mw-content: XbpmnNotations|getPageContent|{{FULLPAGENAME}} }}
-[[Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Inclusive_Gateway-01.png]]
-−
-=== Description ===
-−
-Inclusive Gateways are used for modeling points of synchronization of a number of branches, not all of which are active, after which one or more alternative branches are chosen within a Choreography flow. For example, one of more branches MAY be activated upstream, in parallel, depending on the nature of goods in an order (e.g., large orders, fragile goods orders, orders belonging to pre-existing shipment contracts), and these are subsequently merged. The point of merge results in one or more risk mitigating outcomes (e.g., special insurance protection needed, special packaging needed, and different container categories needed). Inclusive Gateways are also used within an Orchestration Process see page 292.
-−
-Like Exclusive Gateways, Inclusive Gateways are used in a Choreography, but they are constrained by the lack of a central mechanism to store the data that will be used in the Condition expressions of the Gateway’s outgoing Sequence Flows. Choreographies MAY contain natural language descriptions of the Gateway’s Conditions to document the one more alternative paths of the Choreography (e.g., “special insurance protection needed,” “special packaging needed,” and different “container category needed”), but such Choreographies would be underspecified and would not be enforceable. To create an enforceable Choreography, the Gateway Conditions MUST be formal Condition Expressions. In general the following rules apply for the Expressions.
-−
-=== 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::12| ]]
-[[la_pgrel::pg-xbpmn| ]]

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