a.bonita-server.4.1.source-code.XPDL_2_0.xsd Maven / Gradle / Ivy
BPMN extension
Designates the first activity to be executed when the process is instantiated. Used when there is no other way to determine this Conflicts with BPMN StartEvent and no process definition should use both.
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: for Embedded subprocess
BPMN: for Embedded subprocess
BPMN: for Embedded subprocess
Call EJB component -- There can be max one formal parameter that is OUT, if it exists it has to be the last formal parameter. no INOUT formal parameters
Call method on Java class -- There can be max one formal parameter that is OUT, if it exists it has to be the last formal parameter. no INOUT formal parameters
Execute Tranformation -- Formal Parameters restrictions: one IN and one OUT formal parameters or only one INOUT formal parameter
Execute Script -- No additional restrictions for formal parameters. The suggestion: every Formal Parameter should be registered in the script scope as a global variable
For WSDL 1.2 -- Invoke WebService, all IN Fprmal Parameters will be mapped to input message, all OUT Formal Parameters will be maped from output message
The name of inputMessage as defined in the WSDL which will help in uniquely identifying the operation to be invoked
The name of inputMessage as defined in the WSDL which will help in uniquely identifying the operation to be invoked
Invoke business rule
Placeholder for all form related additional information.
BPMN: Not further defined here.
BPMN
BPMN and XPDL
lvalue expression of the assignment, in XPDL may be the name of a DataField, in BPMN name of a Property, in XPATH a reference
rvalue expression of the assignment
BPMN and XPDL
BPMN
BPMN
BPMN (and XPDL??Allows arbitrary grouping of various types of elements, for reporting.)
BPMN and XPDL
BPMN and XPDL
Used in BPMN to support mapping to BPEL
XPDL and BPMN:Maps fields or properties between calling and called processes or subprocesses
XPDL and BPMN:Maps fields between calling and called processes or subprocesses
BPMN
This name should match that specified in Transition/Condition/Expression
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
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?
Formal Parameters defined by WSDL. Must constraint the parameters to either all in or all out, because Message is in a single direction
This must be the name of a Participant
This must be the name of a participant
:BPMN:
BPMN
BPMN: This is used to identify the Activity in an EndEvent Compensation???Also used to associate categories and ocumentation with 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
changes xpdl 1.0 order
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: for Embedded subprocess
BPMN: for Embedded subprocess
BPMN: for Embedded subprocess
BPMN
Should be the Id of an activity which invokes a subflow (independent or embedded) or a task. In the BPMN speck this atribute is called ProcessRef
BPMN: Must be present if if Trigger or ResultType is Compensation.
This supplies the Id of the Activity to be Compensated. Used only for intermediate events or end events in the seuence flow. Events attached to the boundary of an activity already know the Id.
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.
Applicable only to XOR Gateways
BPMN
Required if the Trigger is Message
Used in XPDL and BPMN. In BPMN is equivalent to ProcessRef attribute.
BPMN: needed for independent subprocess
Used to store the instance id of the subflow instantiated by the activity. This is then available later on (e.g. for correlation, messaging etc.) especially in the case of asynchronous invocation.
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.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy