- •1 Scope
- •1.1 General
- •2 Conformance
- •2.1 General
- •2.2 Process Modeling Conformance
- •2.2.1 BPMN Process Types
- •2.2.2 BPMN Process Elements
- •Descriptive Conformance Sub-Class
- •Analytic Conformance Sub-Class
- •Common Executable Conformance Sub-Class
- •2.2.3 Visual Appearance
- •2.2.4 Structural Conformance
- •2.2.5 Process Semantics
- •2.2.6 Attributes and Model Associations
- •2.2.7 Extended and Optional Elements
- •2.2.8 Visual Interchange
- •2.3 Process Execution Conformance
- •2.3.1 Execution Semantics
- •2.3.2 Import of Process Diagrams
- •2.4 BPEL Process Execution Conformance
- •2.5 Choreography Modeling Conformance
- •2.5.1 BPMN Choreography Types
- •2.5.2 BPMN Choreography Elements
- •2.5.3 Visual Appearance
- •2.5.4 Choreography Semantics
- •2.5.5 Visual Interchange
- •2.6 Summary of BPMN Conformance Types
- •3 Normative References
- •3.1 General
- •3.2 Normative
- •3.3 Non-Normative
- •Activity Service
- •BPEL4People
- •Business Process Definition Metamodel
- •Business Process Modeling
- •Business Transaction Protocol
- •Dublin Core Meta Data
- •ebXML BPSS
- •Open Nested Transactions
- •SOAP 1.2
- •UDDI
- •WfMC Glossary
- •Web Services Transaction
- •Workflow Patterns
- •WSBPEL
- •WS-Coordination
- •WSDL
- •WS-HumanTask
- •XML 1.0 (Second Edition)
- •XML-Namespaces
- •XML-Schema
- •XPath
- •XPDL
- •4 Terms and Definitions
- •5 Symbols
- •6 Additional Information
- •6.1 Conventions
- •6.1.1 Typographical and Linguistic Conventions and Style
- •6.1.2 Abbreviations
- •6.2 Structure of this Document
- •6.3 Acknowledgments
- •Submitting Organizations
- •Supporting Organizations
- •Special Acknowledgments
- •7 Overview
- •7.1 General
- •7.2 BPMN Scope
- •7.2.1 Uses of BPMN
- •Private (Internal) Business Processes
- •Public Processes
- •Collaborations
- •Choreographies
- •Conversations
- •Diagram Point of View
- •Understanding the Behavior of Diagrams
- •7.3 BPMN Elements
- •7.3.1 Basic BPMN Modeling Elements
- •7.3.2 Extended BPMN Modeling Elements
- •7.4 BPMN Diagram Types
- •7.5 Use of Text, Color, Size, and Lines in a Diagram
- •7.6 Flow Object Connection Rules
- •7.6.1 Sequence Flow Connections Rules
- •7.6.2 Message Flow Connection Rules
- •7.7 BPMN Extensibility
- •7.8 BPMN Example
- •8 BPMN Core Structure
- •8.1 General
- •8.2 Infrastructure
- •8.2.1 Definitions
- •8.2.2 Import
- •8.2.3 Infrastructure Package XML Schemas
- •8.3 Foundation
- •8.3.1 Base Element
- •8.3.2 Documentation
- •8.3.3 Extensibility
- •Extension
- •ExtensionDefinition
- •ExtensionAttributeDefinition
- •ExtensionAttributeValue
- •Extensibility XML Schemas
- •XML Example
- •8.3.4 External Relationships
- •8.3.5 Root Element
- •8.3.6 Foundation Package XML Schemas
- •8.4 Common Elements
- •8.4.1 Artifacts
- •Common Artifact Definitions
- •Artifact Sequence Flow Connections
- •Artifact Message Flow Connections
- •Association
- •Group
- •Category
- •Text Annotation
- •XML Schema for Artifacts
- •8.4.2 Correlation
- •CorrelationKey
- •Key-based Correlation
- •Context-based Correlation
- •XML Schema for Correlation
- •8.4.3 Error
- •8.4.4 Escalation
- •8.4.5 Events
- •8.4.6 Expressions
- •Expression
- •Formal Expression
- •8.4.7 Flow Element
- •8.4.8 Flow Elements Container
- •8.4.9 Gateways
- •8.4.10 Item Definition
- •8.4.11 Message
- •8.4.12 Resources
- •8.4.13 Sequence Flow
- •Flow Node
- •8.4.14 Common Package XML Schemas
- •8.5 Services
- •8.5.1 Interface
- •8.5.2 EndPoint
- •8.5.3 Operation
- •8.5.4 Service Package XML Schemas
- •9 Collaboration
- •9.1 General
- •9.2 Basic Collaboration Concepts
- •9.2.1 Use of BPMN Common Elements
- •9.3 Pool and Participant
- •9.3.1 Participants
- •PartnerEntity
- •PartnerRole
- •Participant Multiplicity
- •ParticipantAssociation
- •9.3.2 Lanes
- •9.4 Message Flow
- •9.4.1 Interaction Node
- •9.4.2 Message Flow Associations
- •9.5 Conversations
- •9.5.1 Conversation Node
- •9.5.2 Conversation
- •9.5.3 Sub-Conversation
- •9.5.4 Call Conversation
- •9.5.5 Global Conversation
- •9.5.6 Conversation Link
- •9.5.7 Conversation Association
- •9.5.8 Correlations
- •9.6 Process within Collaboration
- •9.7 Choreography within Collaboration
- •9.8 Collaboration Package XML Schemas
- •10 Process
- •10.1 General
- •10.2 Basic Process Concepts
- •10.2.1 Types of BPMN Processes
- •10.2.2 Use of BPMN Common Elements
- •10.3 Activities
- •Sequence Flow Connections
- •Message Flow Connections
- •10.3.1 Resource Assignment
- •Resource Role
- •Expression Assignment
- •Parameterized Resource Assignment
- •10.3.2 Performer
- •10.3.3 Tasks
- •Service Task
- •Send Task
- •Receive Task
- •User Task
- •Manual Task
- •Business Rule
- •Script Task
- •10.3.4 Human Interactions
- •Notation
- •Manual Task
- •User Task
- •Rendering of User Tasks
- •Human Performers
- •Potential Owners
- •XML Schema for Human Interactions
- •Examples
- •10.3.5 Sub-Processes
- •Embedded Sub-Process (Sub-Process)
- •Reusable Sub-Process (Call Activity)
- •Event Sub-Process
- •Transaction
- •Ad-Hoc Sub-Process
- •10.3.6 Call Activity
- •Callable Element
- •10.3.7 Global Task
- •Types of Global Task
- •10.3.8 Loop Characteristics
- •Standard Loop Characteristics
- •Multi-Instance Characteristics
- •Complex Behavior Definition
- •10.3.9 XML Schema for Activities
- •10.4 Items and Data
- •10.4.1 Data Modeling
- •Item-Aware Elements
- •Data Objects
- •DataObject
- •States
- •Data Objects representing a Collection of Data
- •Visual representations of Data Objects
- •Lifecycle and Accessibility
- •Data Stores
- •Properties
- •Lifecycle and Accessibility
- •Data Inputs and Outputs
- •Data Input
- •States
- •Data Output
- •States
- •Service Task Mapping
- •Send Task Mapping
- •Receive Task Mapping
- •User Task Mapping
- •Call Activity Mapping
- •Script Task Mapping
- •Events
- •InputSet
- •OutputSet
- •Data Associations
- •DataAssociation
- •Assignment
- •DataInputAssociation
- •DataOutputAssociation
- •Data Objects associated with a Sequence Flow
- •10.4.2 Execution Semantics for Data
- •Execution Semantics for DataAssociation
- •10.4.3 Usage of Data in XPath Expressions
- •Access to BPMN Data Objects
- •Access to BPMN Data Input and Data Output
- •Access to BPMN Properties
- •For BPMN Instance Attributes
- •10.4.4 XML Schema for Data
- •10.5 Events
- •10.5.1 Concepts
- •Data Modeling and Events
- •Common Event attributes
- •Common Catch Event attributes
- •Common Throw Event Attributes
- •Implicit Throw Event
- •10.5.2 Start Event
- •Start Event Triggers
- •Start Events for Top-level Processes
- •Start Events for Sub-Processes
- •Start Events for Event Sub-Processes
- •Attributes for Start Events
- •Sequence Flow Connections
- •Message Flow Connections
- •10.5.3 End Event
- •End Event Results
- •Sequence Flow Connections
- •Message Flow Connections
- •10.5.4 Intermediate Event
- •Intermediate Event Triggers
- •Intermediate Events in Normal Flow
- •Intermediate Events Attached to an Activity Boundary
- •Attributes for Boundary Events
- •Activity Boundary Connections
- •Sequence Flow Connections
- •Message Flow Connections
- •10.5.5 Event Definitions
- •Event Definition Metamodel
- •Cancel Event
- •Compensation Event
- •Conditional Event
- •Error Event
- •Escalation Event Definition
- •Link Event Definition
- •Message Event Definition
- •Multiple Event
- •None Event
- •Parallel Multiple Event
- •Signal Event
- •Terminate Event
- •Timer Event
- •10.5.6 Handling Events
- •Handling Start Events
- •Handling Events within normal Sequence Flow (Intermediate Events)
- •Handling Events attached to an Activity (Intermediate boundary Events and Event Sub-Processes)
- •Interrupting Event Handlers (Error, Escalation, Message, Signal, Timer, Conditional, Multiple, and Parallel Multiple)
- •Non-interrupting Event Handlers (Escalation, Message, Signal, Timer, Conditional, Multiple, and Parallel Multiple)
- •Handling End Events
- •10.5.7 Scopes
- •10.5.8 Events Package XML Schemas
- •10.6 Gateways
- •10.6.1 Sequence Flow Considerations
- •10.6.2 Exclusive Gateway
- •10.6.3 Inclusive Gateway
- •10.6.4 Parallel Gateway
- •10.6.5 Complex Gateway
- •10.6.6 Event-Based Gateway
- •10.6.7 Gateway Package XML Schemas
- •10.7 Compensation
- •10.7.1 Compensation Handler
- •10.7.2 Compensation Triggering
- •10.7.3 Relationship between Error Handling and Compensation
- •10.8 Lanes
- •10.9 Process Instances, Unmodeled Activities, and Public Processes
- •10.10 Auditing
- •10.11 Monitoring
- •10.12 Process Package XML Schemas
- •11 Choreography
- •11.1 General
- •11.2 Basic Choreography Concepts
- •11.3 Data
- •11.4 Use of BPMN Common Elements
- •11.4.1 Sequence Flow
- •11.4.2 Artifacts
- •11.5 Choreography Activities
- •11.5.1 Choreography Task
- •11.5.2 Sub-Choreography
- •The Parent Sub-Choreography (Expanded)
- •11.5.3 Call Choreography
- •11.5.4 Global Choreography Task
- •11.5.5 Looping Activities
- •11.5.6 The Sequencing of Activities
- •11.6 Events
- •11.6.1 Start Events
- •11.6.2 Intermediate Events
- •11.6.3 End Events
- •11.7 Gateways
- •11.7.1 Exclusive Gateway
- •11.7.2 Event-Based Gateway
- •11.7.3 Inclusive Gateway
- •11.7.4 Parallel Gateway
- •11.7.5 Complex Gateway
- •11.7.6 Chaining Gateways
- •11.8 Choreography within Collaboration
- •11.8.1 Participants
- •11.8.2 Swimlanes
- •Choreography Task in Combined View
- •Sub-Choreography in Combined View
- •11.9 XML Schema for Choreography
- •12 BPMN Notation and Diagrams
- •12.1 BPMN Diagram Interchange (BPMN DI)
- •12.1.1 Scope
- •12.1.2 Diagram Definition and Interchange
- •12.1.3 How to Read this Clause
- •12.2 BPMN Diagram Interchange (DI) Meta-model
- •12.2.1 Overview
- •12.2.2 Abstract Syntax
- •12.2.3 Classifier Descriptions
- •12.2.4 Complete BPMN DI XML Schema
- •12.3 Notational Depiction Library and Abstract Element Resolutions
- •12.3.1 Labels
- •12.3.2 BPMNShape
- •Markers for Activities
- •Tasks [BPMNShape]
- •Collapsed Sub-Processes [BPMNShape]
- •Expanded Sub-Processes [BPMNShape]
- •Collapsed Ad Hoc Sub-Processes [BPMNShape]
- •Expanded Ad Hoc Sub-Processes [BPMNShape]
- •Collapsed Transactions [BPMNShape]
- •Expanded Transactions [BPMNShape]
- •Collapsed Event Sub-Processes [BPMNShape]
- •Expanded Event Sub-Processes [BPMNShape]
- •Call Activities (Calling a Global Task) [BPMNShape]
- •Collapsed Call Activities (Calling a Process) [BPMNShape]
- •Expanded Call Activities (Calling a Process) [BPMNShape]
- •Data [BPMNShape]
- •Events [BPMNShape]
- •Gateways [BPMNShape]
- •Artifacts [BPMNShape]
- •Lanes [BPMNShape]
- •Pools [BPMNShape]
- •Choreography Tasks [BPMNShape]
- •Collapsed Sub-Choreographies [BPMNShape]
- •Expanded Sub-Choreographies [BPMNShape]
- •Call Choreographies (Calling a Global Choreography Task) [BPMNShape]
- •Collapsed Call Choreographies (Calling a Choreography) [BPMNShape]
- •Expanded Call Choreographies (Calling a Choreography) [BPMNShape]
- •Choreography Participant Bands [BPMNShape]
- •Conversations [BPMNShape]
- •12.3.3 BPMNEdge
- •Connecting Objects [BPMNEdge]
- •12.4 Example(s)
- •12.4.1 Depicting Content in a Sub-Process
- •Expanded Sub-Process
- •Expanded Sub-Process with Start and End Events on Border
- •Collapsed Sub-Process
- •12.4.2 Multiple Lanes and Nested Lanes
- •12.4.3 Vertical Collaboration
- •12.4.4 Conversation
- •12.4.5 Choreography
- •13 BPMN Execution Semantics
- •13.1 General
- •13.2 Process Instantiation and Termination
- •13.3 Activities
- •13.3.1 Sequence Flow Considerations
- •13.3.2 Activity
- •13.3.3 Task
- •13.3.4 Sub-Process/Call Activity
- •13.3.5 Ad-Hoc Sub-Process
- •Operational semantics
- •13.3.6 Loop Activity
- •13.3.7 Multiple Instances Activity
- •13.4 Gateways
- •13.4.1 Parallel Gateway (Fork and Join)
- •13.4.2 Exclusive Gateway (Exclusive Decision (data-based) and Exclusive Merge)
- •13.4.3 Inclusive Gateway (Inclusive Decision and Inclusive Merge)
- •13.4.4 Event-based Gateway (Exclusive Decision (event-based))
- •13.4.5 Complex Gateway (related to Complex Condition and Complex Merge)
- •13.5 Events
- •13.5.1 Start Events
- •13.5.2 Intermediate Events
- •13.5.3 Intermediate Boundary Events
- •13.5.4 Event Sub-Processes
- •Operational semantics
- •13.5.5 Compensation
- •Compensation Handler
- •Compensation Triggering
- •Relationship between Error Handling and Compensation
- •Operational Semantics
- •13.5.6 End Events
- •Process level end events
- •Sub-process level end events
- •14 Mapping BPMN Models to WS-BPEL
- •14.1 General
- •14.2 Basic BPMN-BPEL Mapping
- •14.2.1 Process
- •14.2.2 Activities
- •Common Activity Mappings
- •Task Mappings
- •Service Task
- •Receive Task
- •Send Task
- •Abstract Task
- •Service Package
- •Message
- •Interface and Operation
- •Conversations and Correlation
- •Sub-Process Mappings
- •Mapping of Event Sub-Processes
- •Activity Loop Mapping
- •Standard Loops
- •Dealing with LoopMaximum
- •Multi-Instance Activities
- •14.2.3 Events
- •Start Event Mappings
- •Message Start Events
- •Error Start Events
- •Compensation Start Events
- •Intermediate Event Mappings (Non-boundary)
- •Message Intermediate Events (Non-boundary)
- •Timer Intermediate Events (Non-boundary)
- •Compensation Intermediate Events (Non-boundary)
- •End Event Mappings
- •None End Events
- •Message End Events
- •Error End Events
- •Compensation End Events
- •Terminate End Events
- •Boundary Intermediate Events
- •Message Boundary Events
- •Error Boundary Events
- •Compensation Boundary Events
- •Multiple Boundary Events, and Boundary Events with Loops
- •14.2.4 Gateways and Sequence Flows
- •Exclusive (Data-based) Decision Pattern
- •Exclusive (Event-based) Decision Pattern
- •Inclusive Decision Pattern
- •Parallel Pattern
- •Sequence Pattern
- •Structured Loop Patterns
- •Handling Loops in Sequence Flows
- •14.2.5 Handling Data
- •Data Objects
- •Properties
- •Input and Output Sets
- •Data Associations
- •Expressions
- •Assignments
- •14.3 Extended BPMN-BPEL Mapping
- •14.3.1 End Events
- •14.3.2 Loop/Switch Combinations From a Gateway
- •14.3.3 Interleaved Loops
- •14.3.4 Infinite Loops
- •14.3.5 BPMN Elements that Span Multiple WSBPEL Sub-Elements
- •15 Exchange Formats
- •15.1 Interchanging Incomplete Models
- •15.2 Machine Readable Files
- •15.3.1 Document Structure
- •15.3.2 References within the BPMN XSD
- •15.5 XSLT Transformation between XSD and XMI
- •B.1 Scope
- •B.2 Architecture
- •B.3 Diagram Common
- •B.3.1 Overview
- •B.3.2 Abstract Syntax
- •B.3.3 Classifier Descriptions
- •B.4 Diagram Interchange
- •B.4.1 Overview
- •B.4.2 Abstract Syntax
- •B.4.3 Classifier Descriptions
Start Events for Sub-Processes
There is only one type of Start Event for Sub-Processes in BPMN (see Figure 10.82): None.
Table 10.85 – Sub-Process Start Event Types
Trigger |
Description |
Marker |
|
|
|
None |
The None Start Event is used for all Sub-Processes, either embedded |
|
|
or called (reusable). Other types of triggers are not used for a |
|
|
Sub-Process, since the flow of the Process (a token) from the parent |
|
|
Process is the trigger of the Sub-Process. If the Sub-Process is called |
|
|
(reusable) and has multiple Start Events, some of the other Start Events |
|
|
MAY have triggers, but these Start Events would not be used in the |
|
|
context of a Sub-Process. When the other Start Events are triggered, |
|
|
they would instantiate top-level Processes. |
|
|
|
|
Start Events for Event Sub-Processes
A Start Event can also initiate an inline Event Sub-Process (see page 174). In that case, the same Event types as for boundary Events are allowed (see Table 10.86), namely: Message, Timer, Escalation, Error, Compensation,
Conditional, Signal, Multiple, and Parallel.
An Event Sub-Process MUST have a single Start Event.
Table 10.86 – Event Sub-Process Start Event Types
Trigger |
Description |
Marker |
||
|
|
|
|
|
Message |
If there is only one EventDefinition associated with the Start Event and |
Interrupting |
||
|
that EventDefinition is of the subclass MessageEventDefinition, |
|
|
|
|
then the Event is a Message Start Event and uses an envelope marker (see |
|
|
|
|
|
|
|
|
|
the |
|
|
|
|
|
|
|
|
|
figures to the right). |
Non- |
||
|
• For a Message Event Sub-Process that interrupts its containing |
|||
|
Process, the boundary of the Event is solid (see the upper figure to the |
Interrupting |
||
|
right). |
|
|
|
|
• For a Message Event Sub-Process that does not interrupt its |
|
|
|
|
|
|
|
|
|
containing |
|
|
|
|
|
|
|
|
|
Process, the boundary of the Event is dashed (see the lower figure on |
|
|
|
|
the right). |
|
|
|
|
The actual Participant from which the Message is received can be identified |
|
|
|
|
by connecting the Event to a Participant using a Message Flow within the |
|
|
|
|
definitional Collaboration of the Process – see Table 10.1. |
|
|
|
|
|
|
|
|
Business Process Model and Notation (BPMN), v2.0.2 |
241 |
Table 10.86 – Event Sub-Process Start Event Types
Timer |
If there is only one EventDefinition associated with the Start Event and |
Interrupting |
|
that EventDefinition is of the subclass TimerEventDefinition, then |
|
|
the Event is a Timer Start Event and uses a clock marker (see the figures to |
|
|
the right). |
|
|
• For a Timer Event Sub-Process that interrupts its containing Process, |
Non- |
|
the boundary of the Event is solid (see the upper figure to the right). |
|
|
• For a Timer Event Sub-Process that does not interrupt its containing |
Interrupting |
|
|
|
|
Process, the boundary of the Event is dashed (see the lower figure on |
|
|
the right). |
|
|
|
|
Escalation |
Escalation Event Sub-Processes implement measures to expedite the |
Interrupting |
|
completion of a business Activity, should it not satisfy a constraint specified |
|
|
on its execution (such as a time-based deadline). |
|
|
The Escalation Start Event is only allowed for triggering an in-line Event |
|
|
Sub-Process. |
|
|
If there is only one EventDefinition associated with the Start Event and |
Non- |
|
that EventDefinition is of the subclass EscalationEventDefinition, |
Interrupting |
|
then the Event is an Escalation Start Event and uses an arrowhead marker |
|
|
(see the figures to the right). |
|
|
For an Escalation Event Sub-Process that interrupts its containing Process, |
|
|
the boundary of the Event is solid (see the upper figure to the right). |
|
|
For an Escalation Event Sub-Process that does not interrupt its containing |
|
|
Process, the boundary of the Event is dashed (see the lower figure on the |
|
|
right). |
|
|
|
|
Error |
The Error Start Event is only allowed for triggering an in-line Event Sub- |
Interrupting |
|
Process. |
|
|
If there is only one EventDefinition associated with the Start Event and |
|
|
that EventDefinition is of the subclass ErrorEventDefinition, then |
|
|
the Event is an Error Start Event and uses a lightning marker (see the figures |
|
|
to the right). |
|
|
Given the nature of Errors, an Event Sub-Process with an Error trigger will |
|
|
always interrupt its containing Process. |
|
|
|
|
Compensation |
The Compensation Start Event is only allowed for triggering an in-line |
|
|
Compensation Event Sub-Process (see “Compensation Handler” on page |
|
|
302). This type of Event is triggered when compensation occurs. |
|
|
If there is only one EventDefinition associated with the Start Event and |
|
|
that EventDefinition is of the subclass |
|
|
CompensationEventDefinition, then the Event is a Compensation |
|
|
Start Event and uses a double triangle marker (see the figure to the right). |
|
|
This Event does not interrupt the Process since the Process has to be |
|
|
completed before this Event can be triggered. |
|
|
|
|
242 |
Business Process Model and Notation (BPMN), v2.0.2 |
Table 10.86 – Event Sub-Process Start Event Types
Conditional |
If there is only one EventDefinition associated with the Start Event and |
Interrupting |
|||
|
that EventDefinition is of the subclass ConditionalEventDefini- |
|
|
|
|
|
tion, then the Event is a Conditional Start Event and uses an lined page |
|
|
|
|
|
marker (see the figures to the right). |
|
|
|
|
|
|
|
|
|
|
|
For a Conditional Event Sub-Process that interrupts its containing Process, |
|
|
|
|
|
then the boundary of the Event is solid (see the upper figure to the right). |
Non- |
|||
|
For a Conditional Event Sub-Process that does not interrupt its containing |
Interrupting |
|||
|
Process, the boundary of the Event is dashed (see the lower figure on the |
|
|
|
|
|
right). |
|
|
|
|
Signal |
If there is only one EventDefinition associated with the Start Event and |
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
||
Interrupting |
||||||
|
that EventDefinition is of the subclass SignalEventDefinition, then |
|
|
|
|
|
|
the Event is a Signal Start Event and uses an triangle marker (see the fig- |
|
|
|
|
|
|
ures to the right). |
|
|
|
|
|
|
For a Signal Event Sub-Process that interrupts its containing Process, then |
|
|
|
|
|
|
the boundary of the Event is solid (see the upper figure to the right). |
Non- |
||||
|
For a Signal Event Sub-Process that does not interrupt its containing |
Interrupting |
||||
|
Process, the boundary of the Event is dashed (see the lower figure on the |
|
|
|
|
|
|
right). |
|
|
|
|
|
Multiple |
A Multiple Event indicates that there are multiple ways of triggering the |
Interrupting |
|
Event Sub-Process. Only one of them is REQUIRED to actually start the |
|
|
Event Sub-Process. There is no specific EventDefinition subclass (see |
|
|
page 259) for Multiple Start Events. If the Start Event has more than one |
|
|
associated EventDefinition, then the Event MUST be displayed with the |
Non- |
|
Multiple Event marker (a pentagon—see the figures on the right). |
|
|
For a Multiple Event Sub-Process that interrupts its containing Process, the |
Interrupting |
|
boundary of the Event is solid (see the upper figure to the right). |
|
|
For a Multiple Event Sub-Process that does not interrupt its containing |
|
|
Process, the boundary of the Event is dashed (see the lower figure on the |
|
|
right). |
|
Business Process Model and Notation (BPMN), v2.0.2 |
243 |
Table 10.86 – Event Sub-Process Start Event Types
Parallel
Multiple
A Parallel Multiple Event indicates that there are multiple ways of triggering the Event Sub-Process. All of them are REQUIRED to actually start the Event Sub-Process. There is no specific EventDefinition subclass (see page 259) for Parallel Multiple Start Events. If the Start Event has more than one associated EventDefinition and the parallelMultiple attribute of the Start Event is true, then the Event MUST be displayed with the Parallel Multiple Event marker (an open plus sign—see the figures to the
right).
For a Parallel Multiple Event Sub-Process that interrupts its containing
Process, the boundary of the Event is solid (see the upper figure to the right). For a Parallel Multiple Event Sub-Process that does not interrupt its containing Process, the boundary of the Event is dashed (see the lower figure on the right).
Interrupting
Non-
Interrupting
Attributes for Start Events
For Start Events, the following additional attribute exists:
•The Start Event element inherits the attributes and model associations of CatchEvent (see Table 10.82). Table 10.87 presents the additional attributes of the Start Event element:
Table 10.87 – Start Event attributes
Attribute Name |
Description/Usage |
isInterrupting: boolean = This attribute only applies to Start Events of Event Sub-Processes; it is ignored for true other Start Events. This attribute denotes whether the Sub-Process encompassing
the Event Sub-Process should be canceled or not, If the encompassing SubProcess is not canceled, multiple instances of the Event Sub-Process can run concurrently. This attribute cannot be applied to Error Events (where it’s always true), or Compensation Events (where it doesn’t apply).
Sequence Flow Connections
See “Sequence Flow Connections Rules” on page 40 for the entire set of objects and how they MAY be a source or target of a Sequence Flow.
A Start Event MUST NOT be a target for Sequence Flows; it MUST NOT have incoming Sequence Flows.
An exception to this is when a Start Event is used in an Expanded Sub-Process and is attached to the boundary of that Sub-Process. In this case, a Sequence Flow from the higher-level Process MAY connect to that Start Event in lieu of connecting to the actual boundary of the Sub-Process.
A Start Event MUST be a source for a Sequence Flow.
Multiple Sequence Flows MAY originate from a Start Event. For each Sequence Flow that has the Start Event as a source, a new parallel path SHALL be generated.
The conditionExpression attribute for all outgoing Sequence Flows MUST be set to None.
244 |
Business Process Model and Notation (BPMN), v2.0.2 |