Enumeration of the following literal values: Enumeration of the following literal values: Enumeration of the following literal values: A Transaction is a kind of Embedded Process which enclosed activity (ies) can be rolled back by the mean of an Actor. Inclusive Decision is a Parallel Split that has an outgoing Succession specified as the default if none of the other outgoing successions apply due their conditions. An Inclusive Merge is a Gateway that requires none of the upstream activities to be executing for the join to apply. An Artifact Flow is a Simple Interaction which has the following characteristics: . It has a Holder as one of its Interactive Parts. . The other interactive part is an Activity. . If this Activity is the source interactive part , it has a next succession to the Artifact Flow. . If this Activity is the target interactive part , it has a previous succession from the Artifact Flow. A Holder is an Interactive Part storing items temporarily as they flow through the Process. For example, a document, phone number, or package can flow along simple interactions, into a holder for some period, and flow out later. The type of the Holder is the type of thing it can hold. A Processor Role is the top-level Performer Role reponsible for all activities and interactions at the boundary of the Process. As all Performer Roles, it can delegate responsibility for a subset of the process activities and interactions to Performer Roles, which in can turn delegate smaller subsets to other Performer Roles (delegated performer role ). A Processor Role may be active or passive. An active processor will control and/or monitor the process and may manage process resources. A passive processor delegates all responsibilities to delegee role. The actor of a passive processor may be a "community", consensus body or group of actors who have agreed to work together in a particular way. The actor of an active processor must be an individual, system or organization capable of taking action, initiating and responding to Interactions and managing resources. An Abort Activity is a Simple Activity that interrupts the course of a Process. All activities in the Process should be immediately ended. The Process is ended without compensation or event handling. The type of all Abort Activity(ies) must be Abort Process provided by the BPMN Library for the Activity Model (Activity Library) An Embedded Process is a kind of Behavior Step Group that groups a set of Activity that, as a whole, act as a Behavior Step . Thereby, an Embedded Process is typed by a Course that defines its start change and a finish change . As any Behavior Step, an Embedded Process can be interrupted or constrained in its Course course. An Actor is an entity that is responsible for the execution of duties specified by a Performer Role Further sub-type of Actor will be defines in specifications such as the the Organizational Structure Metamodel (OSM) to add specific requirements such as and can as having certain skills or budget. An Artifact Sequence Flow is a Simple Interaction that has the following characteristics: . Its Interactive Part are activities. . The source interactive part has a next succession to the Artifact Sequence Flow . A Simple Activity is an Activity which process type is no further composed of other activities A Sub-Process Activity is an Activity which process type is further composed of other activities A Cancel Activity is a kind of Simple Activity that causes the Cancel Event of its enclosing Course In case where the Cancel Activity is part of an Embedded Process, the cancelled Course is this Embedded Process, otherwise the cancelled Course is the Process that owns the Cancel Activity Sequences Flow is Succession from one part to another (see Course). If the source part of the succession is typed (not a Gateway), then if the source part has no intermediate events attached, the source end refers to the end part (which can be omitted as the default), otherwise to the finish part. If the target part is typed, then the target part refers to the start part (which can be omitted as the default). Same as Exclusive Split but with a different name in BPMN A role realization takes a realized performer role and defines a processor role and the associated process that specifies the specific process to be enacted by the specified processor role as required to meet the responsibilities of the realized performer role. A performer role may be realized by any number of processor roles as long as they each satisfy the responsibilities of the role. Same as Exclusive Join but with a different name in BPMN The Process Interaction Boundary is the Interaction Role through which a Process interacts to get its inputs and deliver its outputs. The process is responsible to fulfill all Interactions attached to the Process Interaction Boundary. A Complex Decision is a Parallel Split that has an expression determining which outgoing Successions apply. An Error Activity is a kind of Simple Activity that produces an Error Event and that ends its enclosing Course In case where the Error Activity is part of an Embedded Process, the ended Course is this Embedded Embedded Process, otherwise the ended Course is the Process that owns the Error Activity. A Complex Merge is an Exclusive Join that has an expression determining which which incoming Successions must apply for the merge to apply. BPMN name for Simple Activity Conditional Loop is a kind of Activity Loop that will execute its enclosed activities multiple times as a group while a specified condition is true. If the condition is never true, the enclosed activities are never executed. The multiple subexecutions are sequential. A Substitutable Derivation is a kind of Derivation that derives one Process from another and that does not alter the Interaction at the owned process interaction boundary A Compensating Activity is an Activity that follows an Event Monitor conditionned by the Compensate Event Event. A Compensating Activity cannot have successors. Terminate is the BPMN name for Abort Activity Multi Instance Loop is a kind of Activity Loop that will execute its enclosed activities as a group of times, as specified by the number of instances ValueSpecification evaluated at the time the loop begins executing. A Multi Instance Loop supports the option of sequential or parallel subexecutions as specified by its ordering attribute. An Event Decision applies a race connector to the parts on the target end of Successions that have the event decision as source (see Behavior). The targeted parts are Event Monitors. To wait for incoming messages, these can include Event Monitors detecting the finish of simple interactions from the boundary to the processor role. A Performer Role is a Part Group that takes responsibility of performing activities in the process. Being an Interactive Part, a Performer Role also has responsibilities to fulfill Interactions that it is involved with other Performer Roles or with Interaction Roles at the boundary of the Process. A Performer Role is a Typed Part for specifying Actor that can play the role at process enactment. A Performer Role can be decomposed into sub Performer Role to delegate responsibility for a subset of its activities or interactions. A Performer Role may have a realization as defined by a Role Realization that further specifies how the Performer Role will meet its responsibilities. An Activity is a kind of Behavior Step that activates a Behavior (it operates over time) in the context of a Process. It can: be ordered in time by Succession operate under the responsibility of a Performer Role activate a sub-processe or be a simple task that start and stop An Activity is also an Interactive Part that receives its inputs and outputs through Interactions coming from other Interactive Parts in the Process (Activity, Interaction Role, Performer Role, Holder). Compensate Activity is a kind of Simple Activity that ends a Process and indicates that a Compensation is necessary. An Activity Loop is an Embedded Process that can execute its enclosed activities multiple times. The process can proceed past the loop in several ways: After all subexecutions are complete, with a succession that has the loop as the source. After each subexecution, with succession that has the iterationEnd behavior part as an internal source. This part is defined in a user (M1) library in the Activity Model, typed by the IterationEnd change also defined in the library. After the first subexecution to complete, with a succession that has the IterationEnd as an internal source, and a guard evaluating to the string "first iteration". After each subexecution, but depending on conditions, with a succession that has the iterationEnd behavior part as an internal source, and a guard specified by the modeler. A Process is a kind of Interactive Behavior that describes specific Activity(ies) to be performed, Interactions to be undertaken during its execution under the authority of a Processor Role (or delegated performer role s). The process owns the set of activities to be performed as well as the Conditions on when such activities will be performed and by which performer role. The process also owns the set of Interactive Parts that define the flow of information and other resources between activities,Performer Role and Interaction Roles. A specific Interaction Role defines the set of Interactions the process is responsible of: its is the Process Interaction Boundary. The set of Interactions attached to the Process Interaction Boundary defines the inputs and outputs of the process A Process may utilize sub-processes with a Sub-Process Activity as well as be used in the context of other processes in the same way.