Types used in the BPMN specification.
| CLASS | DESCRIPTION |
|---|---|
AdHocOrdering |
This attribute defines if the Activities within the Process can be performed in parallel or sequentially. |
AssociationDirection |
Defines whether the Association shows any directionality with an arrowhead. |
ChoreographyLoopType |
Determines the appropriate marker for a Choreography Activity that repeats. |
EventBasedGatewayType |
Determines the behavior of the Gateway when used to instantiate a Process. |
GatewayDirection |
Constraints on how the Gateway MAY be used. |
ImplementationValue |
Specifies the technology that will be used to send and receive the Messages. |
ItemKind |
Specifies the nature of an item, which can be a physical or information item. |
MultiInstanceFlowCondition |
The behavior of a multi-instance loop. |
ProcessType |
Provides additional information about the level of abstraction modeled by this Process. |
RelationshipDirection |
This attribute specifies the direction of a relationship. |
StartEventType |
This attribute specifies the type of Start Event. |
TransactionMethodValue |
Defines the Transaction method used to commit or cancel a Transaction. |
Classes¶
Bases: StrEnum
This attribute defines if the Activities within the Process can be performed in parallel or sequentially.
Bases: StrEnum
Constraints on how the Gateway MAY be used.
• Unspecified: There are no constraints. The Gateway MAY have any number of incoming and outgoing Sequence Flows. • Converging: This Gateway MAY have multiple incoming Sequence Flows but MUST have no more than one (1) outgoing Sequence Flow. • Diverging: This Gateway MAY have multiple outgoing Sequence Flows but MUST have no more than one (1) incoming Sequence Flow. • Mixed: This Gateway contains multiple outgoing and multiple incoming Sequence Flows.