BPMN extension BPMN: Status values are assigned during execution. Status can be treated as a property and used in expressions local to an Activity. It is unclear that status belongs in the XPDL document. BPMN and XPDL In XPDL should be name of a DataField, in BPMN name of a Property BPMN and XPDL BPMN: Not further defined here. BPMN (and XPDL??Allows arbitrary grouping of various types of elements, for reporting.) XPDL and BPMN:Maps fields or properties between calling and called processes or subprocesses XPDL and BPMN:Maps fields or properties between calling and called processes or subprocesses BPMN BPMN Required if the Trigger or Result is Message BPMN BPMN BPMN BPMN BPMN Required if the Trigger is Message A Target MAY be included for the Intermediate Event. The Target MUST be an activity (Sub-Process or Task). This means that the Intermediate Event is attached to the boundary of the activity and is used to signify an exception or compensation for that activity. BPMN BPMN (and possibly XPDL) BPMN This is updated at run time to count the number of executions of the loop and is available as a property to be used in expressions. Does this belong in the XPDL? BPMN This is updated at run time to count the number of executions of the loop and is available as a property to be used in expressions. Does this belong in the XPDL? This must be the name of a Participant This must be the name of a participant BPMN: This is used to identify the Activity in an EndEvent Compensation???Also used to associate categorieswith a variety of elements This identifies any Object in the BPMN diagram. BPMN BPMN BPMN A String or Expression designating the Performer BPMN and XPDL BPMN BPMN BPMN BPMN: Like fields in XPDL BPMN: Must be present if if Trigger or ResultType is Compensation. This supplies the Object of the Activity to be Compensated. This doesn't seem to make sense. See the definition of Object. BPMN: Must be present if Trigger or ResultType is error. BPMN: Must be present if ResultType is Multiple. at least two results must be present Used when needed for BPMN Gateways. Gate and sequence information is associated with the Transition Element. Used only when GatewayType is XOR. Used when needed for BPMN Gateways Applicable only to XOR Gateways Applicable only to complex gateways Applicable only to Complex Gateways BPMN Required if the Trigger is Message BPMN BPMN BPMN BPMN: for Embedded subprocess BPMN: for Embedded subprocess BPMN: for Embedded subprocess BPMN: needed for independent subprocess BPMN: needed for independent subprocess BPMN: Required when subprocess type is Reference. BPMN BPMN: BPMN BPMN Required if the Task is Receive BPMN BPMN Required if the Task is Send BPMN Required if the Task is Service BPMN BPMN BPMN Required if the Task is User BPMN: If SubProcess is a transaction then this is required. Used only in BPMN. Specifies number of tokens on outgoing transition. BPMN: if the Trigger or Result Type is Link then this must be present. This must identify a Process. Should be the Id of a process. BPMN: If the Trigger or Result Type is Message then this must be present BPMN: if the TriggerType is Multiple then this must be present. BPMN: For Multiple, at least two triggers must be present. BPMN: if the TriggerType is Multiple then this must be present. BPMN: For Multiple, at least two triggers must be present. BPMN: if the TriggerType is Rule then this must be present. This is the nameof a Rule element. BPMN: If the Trigger Type is Timer then this must be present One of TimeDate or TimeCycle must be present BPMN:: If the Implementation is a WebService this is required. Must be the name of a Participant: Note, this will map to the BPEL4WS partnerLink. (aka portType) BPMN: BPMN: Status values are assigned during execution. Status can be treated as a property and used in expressions local to a Process. It is unclear that status belongs in the XPDL document. BPMN BPMN BPMN