Complex Gateway - Revision history

Admin at 13:00, 3 May 2017

2017-05-03T13:00:36Z

Admin at 12:35, 30 September 2015

2015-09-30T12:35:07Z

Admin at 07:47, 18 September 2015

2015-09-18T07:47:47Z

Admin: Created page with "{{DISPLAYTITLE:Complex Gateway}} Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Complex_Gateway-01.png === Description === Complex Gateways can model partia..."

2015-09-17T14:37:22Z

Created page with "{{DISPLAYTITLE:Complex Gateway}} Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Complex_Gateway-01.png === Description === Complex Gateways can model partia..."

New page

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

=== Description ===

Complex Gateways can model partial merges in Business Processes where when some but not all of a set of preceding branches complete, the Gateway fires. This can be considered the discriminator/n-of-m join pattern1 and is not supported through the inclusive OR merge since it is not concerned with sets of branches, but rather branches that have tokens. Applied in Choreographies, Complex Gateways can model tendering and information canvassing use cases where requests are sent to participants who respond at different times.

Consider an e-tender that sends a request for quote to multiple service providers (e.g., warehouse storage) in a marketplace. The e-tender Process sends out requests to each service provider and anticipates their response through three Choreography Activities. The response branches merge at a Complex Gateway to model the requirement that when 66% responses have arrived, an assessment of the tender can proceed. The assessment occurs after the Complex Gateway. If the assessment reports that the reserve amount indicated by the customer cannot be met, a new iteration of the tender is made. A key issue is to ensure that the responses should not be mixed across tender iterations. A Terminate End Event ensures that all Activities are terminated, when a tender has been successful.

=== 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::17| ]]
[[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:Complex Gateway}}
+{{DISPLAYTITLE:Complex Gateway}}{{#lead-mw-content: XbpmnNotations|getPageContent|{{FULLPAGENAME}} }}
-[[Has image::File:LEAD_BPMN_2.0_-_Visio_Stencils_-_Gateways_-_Complex_Gateway-01.png]]
-−
-=== Description ===
-−
-Complex Gateways can model partial merges in Business Processes where when some but not all of a set of preceding branches complete, the Gateway fires. This can be considered the discriminator/n-of-m join pattern1 and is not supported through the inclusive OR merge since it is not concerned with sets of branches, but rather branches that have tokens. Applied in Choreographies, Complex Gateways can model tendering and information canvassing use cases where requests are sent to participants who respond at different times.
-−
-Consider an e-tender that sends a request for quote to multiple service providers (e.g., warehouse storage) in a marketplace. The e-tender Process sends out requests to each service provider and anticipates their response through three Choreography Activities. The response branches merge at a Complex Gateway to model the requirement that when 66% responses have arrived, an assessment of the tender can proceed. The assessment occurs after the Complex Gateway. If the assessment reports that the reserve amount indicated by the customer cannot be met, a new iteration of the tender is made. A key issue is to ensure that the responses should not be mixed across tender iterations. A Terminate End Event ensures that all Activities are terminated, when a tender has been successful.
-−
-=== 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::17| ]]
-[[la_pgrel::pg-xbpmn| ]]

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