Editing BPMN (section)

=====Sub-Process=====
* Sub-Types are:
** [[#Ad-hoc_Sub-Process|Ad-Hoc Sub-Process]]
** [[#Event_Sub-Process|Event Sub-Process]]
** [[#Transaction_Sub-Process|Transaction Sub-Process]]
* Markers are:
** Loop
** Multi-instance
** Compensation
** Ad-Hoc
** Compensation and Ad-Hoc
* must start with at least one undefined Start Event, but more than one are confusing
* Start Event can be drawn to the boundary
* if a pool is used the name must be the same as the parent process, if there is no pool there is an implicit one of the parent process
* can also shown in a BPD inline/expanded
* can be an embedded Sub-Process or an global Sub-Process
** Embedded Sub-Process may only have on None Start Event
** Embedeed Sub-Process may not have an pools or lanes
** Embedeed Sub-Process have access to the parent process data
* may contain lanes
* completes when all tokens have reached an End Event
* the exception flow happens immediately, triggering the next downstream, the sequence flow (normal flow) does not get executed

======Ad-hoc Sub-Process======

An Ad-Hoc Sub-Process or Process contains a number of embedded inner Activities and is intended to be executed with a more flexible. The Ad-Hoc Sub-Process contains only Activities, Sequence Flows, Gateways, and Intermediate Events. An Ad-Hoc Sub-Process may also contain Data Objects and Data Associations. The Activities within the Ad-Hoc Sub-Process are not required to have incoming and outgoing Sequence Flows. However, it is possible to specify Sequence Flows between some of the contained Activities. The contained Activities are executed sequentially or in parallel, they can be executed multiple times in an order that is only constrained through the specified Sequence Flows, Gateways, and data connections. After completion of an inner activity an completion condition is evaluated, so the sub-process might be completed by meeting the condition without having started some of the activities.

======Event Sub-Process======
* allow to handle an Event within the context of a given Sub-Processes or Process
* is a specialized Sub-Process that is used within a Process (or Sub-Process)
* when the triggeredbyEvent attribute of Sub-Process is true
* has no in-coming and out-going sequence flows
* MAY or MAY NOT occur while the parent Process is active, but it is possible that it will occur many times
* An Event Sub-Process MUST have one and only one Start Event
* has access to all data of the surrounding Sub-Process
* they cannot have attached boundary Events
* becomes initiated, and thus Enabled and Running, through the Activity to which it is attached
* There are two possible consequences to the parent Process when an Event Sub-Process is triggered:
** the parent Process can be interrupted (cancels execution of the enclosing Sub-Process, identified by an interrupting start event (if the isInterrupting attribute of its Start Event is set))
** the parent Process can continue its work (not interrupted, identified with an Non-interrupting Start Event) (enclosed runs parallel)
* If the parent Activity enters the state Completing, it remains in that state until all contained active Event Sub-Processes have completed.On the other hand the subsequent Activity of the Sub-Process with the Event Sub-Process will not be triggered until all Activities within the Sub-Process are finalized although the Event Sub-Process is already completed.
* there are special Event Sub-Processes
** [[#CompensationEventSubProcess|Compensation Event Sub-Process]]

<span id="CompensationEventSubProcess">'''Compensation Event Sub-Process'''</span>
* A Compensation Event Sub-Process can recursively trigger compensation for Activities contained in its parent (see OMG spec example)

======Transaction Sub-Process======
* A Transaction is a specialized type of Sub-Process that will have a special behavior that is controlled through a transaction protocol (such as WS-Transaction).