Designing and Implementing Business Process Models : Modeling BPMN 1.x in ARIS : Semantic Checks : Sequence Flow/Message Flow
Sequence Flow/Message Flow
Attribute Rules
5
For Sequence Flows which have the Condition Type set to Expression the attribute Condition Expression must be maintained.
AT_BPMN_SEQ_FLOW_CONDITION AT_BPMN_CONDITION_EXPRESSION
6
If a sequence flow has its attribute Condition set to Default / not maintained the Condition Expression MUST NOT be maintained
 
7
A sequence flow which originates from an Event MUST NOT have a maintained Condition Attribute.
 
Structure Rules
8
A Sequence Flow MUST NOT cross the boundary of a (sub)process.
(Source and Target of a Sequence Flow MUST not cross Pool boundaries (but they can cross lane boundaries).
(both elements are part of the same pool (direct or via lanes that belong to a pool) or both elements are part of the inherited pool (pool is placed in a superior model)
For the expanded SubProcess: Both elements must be part of the same subprocess element.
9
A message flow MUST cross Pool boundaries.
Inverse logic of the sequence flows.
10
If an activity has only one outgoing sequence flow this flow MUST NOT be conditional.
 
11
Compensation, Cancel and Error Events which have an incoming may trigger connection must overlap the source of the may trigger connection. (share some pixels).
 
The source of a normal is created by Sequence Flow Connections MUST NOT overlap its target. (share some pixels with the target object).
(from an activity / sub process towards an intermediate event).
Copyright © 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback