Sequence Flow - Revision history

Admin at 12:59, 3 May 2017

2017-05-03T12:59:37Z

Admin at 12:34, 30 September 2015

2015-09-30T12:34:31Z

Admin at 08:15, 23 September 2015

2015-09-23T08:15:50Z

Admin at 07:25, 18 September 2015

2015-09-18T07:25:20Z

Admin: Created page with "{{DISPLAYTITLE:Sequence Flow}} Has image::File:Sequence_Flow-01.png === Description === The nature and behavior of Sequence Flows is described in “Sequence Flow” on..."

2015-09-17T11:59:35Z

Created page with "{{DISPLAYTITLE:Sequence Flow}} Has image::File:Sequence_Flow-01.png === Description === The nature and behavior of Sequence Flows is described in “Sequence Flow” on..."

New page

{{DISPLAYTITLE:Sequence Flow}}
[[Has image::File:Sequence_Flow-01.png]]

=== Description ===

The nature and behavior of Sequence Flows is described in “Sequence Flow” on page 97. But there are special considerations relative to Sequence Flows when applied to Activities. An Activity that is the target of multiple Sequence Flows participates in “uncontrolled flow.”

To facilitate the definition of Sequence Flow (and other Process elements) behavior, we employ the concept of a token that will traverse the Sequence Flows and pass through the elements in the Process. A token is a theoretical concept that is used as an aid to define the behavior of a Process that is being performed. The behavior of Process elements can be defined by describing how they interact with a token as it “traverses” the structure of the Process. However, modeling and execution tools that implement BPMN are NOT REQUIRED to implement any form of token.

Uncontrolled flow means that, for each token arriving on any incoming Sequence Flows into the Activity, the Task will be enabled independently of the arrival of tokens on other incoming Sequence Flows. The presence of multiple incoming Sequence Flows behaves as an exclusive gateway. If the flow of tokens into the Task needs to be ‘controlled,’ then Gateways (other than Exclusive) should be explicitly included in the Process flow prior to the Task to fully eliminate semantic ambiguities.

If an Activity has no incoming Sequence Flows, the Activity will be instantiated when the containing Process or Sub-Process is instantiated. Exceptions to this are Compensation Activities, as they have specialized instantiation behavior.

Activities can also be source of Sequence Flows. If an Activity has multiple outgoing Sequence Flows, all of them will receive a token when the Activity transitions to the Completed state. Semantics for token propagation for other termination states is defined below. Thus, multiple outgoing Sequence Flows behaves as a parallel split. Multiple outgoing Sequence Flows with conditions behaves as an inclusive split. A mix of multiple outgoing Sequence Flows with and without conditions is considered as a combination of a parallel and an inclusive split as shown in the Figure 13.1.

If the Activity has no outgoing Sequence Flows, the Activity will terminate without producing any tokens and termination semantics for the container is then applied.

Token movement across a Sequence Flow does not have any timing constraints. A token might take a long or short time to move across the Sequence Flow. If the is Immediate attribute of a Sequence Flow has a value of false, or has no value and is taken to mean false, then Activities not in the model MAY be executed while the token is moving along the Sequence Flow. If the is Immediate attribute of a Sequence Flow has a value of true, or has no value and is taken to mean true, then Activities not in the model MAY NOT be executed while the token is moving along the Sequence Flow.

=== 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::Flows]]

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

[[la_position::1| ]]
[[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:Sequence Flow}}
+{{DISPLAYTITLE:Sequence Flow}}{{#lead-mw-content: XbpmnNotations|getPageContent|{{FULLPAGENAME}} }}
-[[Has image::File:Sequence_Flow-01.png]]
-−
-=== Description ===
-−
-The nature and behavior of Sequence Flows is described in "Sequence Flow" on page 97. But there are special considerations relative to Sequence Flows when applied to Activities. An Activity that is the target of multiple Sequence Flows participates in "uncontrolled flow."
-−
-To facilitate the definition of Sequence Flow (and other Process elements) behavior, we employ the concept of a token that will traverse the Sequence Flows and pass through the elements in the Process. A token is a theoretical concept that is used as an aid to define the behavior of a Process that is being performed. The behavior of Process elements can be defined by describing how they interact with a token as it “traverses” the structure of the Process. However, modeling and execution tools that implement BPMN are NOT REQUIRED to implement any form of token.
-−
-Uncontrolled flow means that, for each token arriving on any incoming Sequence Flows into the Activity, the Task will be enabled independently of the arrival of tokens on other incoming Sequence Flows. The presence of multiple incoming Sequence Flows behaves as an exclusive gateway. If the flow of tokens into the Task needs to be ‘controlled,’ then Gateways (other than Exclusive) should be explicitly included in the Process flow prior to the Task to fully eliminate semantic ambiguities.
-−
-If an Activity has no incoming Sequence Flows, the Activity will be instantiated when the containing Process or Sub-Process is instantiated. Exceptions to this are Compensation Activities, as they have specialized instantiation behavior.
-−
-Activities can also be source of Sequence Flows. If an Activity has multiple outgoing Sequence Flows, all of them will receive a token when the Activity transitions to the Completed state. Semantics for token propagation for other termination states is defined below. Thus, multiple outgoing Sequence Flows behaves as a parallel split. Multiple outgoing Sequence Flows with conditions behaves as an inclusive split. A mix of multiple outgoing Sequence Flows with and without conditions is considered as a combination of a parallel and an inclusive split as shown in the Figure 13.1.
-−
-If the Activity has no outgoing Sequence Flows, the Activity will terminate without producing any tokens and termination semantics for the container is then applied.
-−
-Token movement across a Sequence Flow does not have any timing constraints. A token might take a long or short time to move across the Sequence Flow. If the is Immediate attribute of a Sequence Flow has a value of false, or has no value and is taken to mean false, then Activities not in the model MAY be executed while the token is moving along the Sequence Flow. If the is Immediate attribute of a Sequence Flow has a value of true, or has no value and is taken to mean true, then Activities not in the model MAY NOT be executed while the token is moving along the Sequence Flow.
-−
-=== 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::Flows]]
 === Reference Content ===
@@ Line 41: / Line 15: @@
 *Transformation Benchmarking Reference Content
 *Innovation Reference Content

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