a.bonita-server.5.0.M4.source-code.XPDL_2_1.xsd Maven / Gradle / Ivy
BPMN: corresponds to a flow object, which could be a BPMN activity, gateway, or event
BPMN extension
BPMN: corresponds to an activity, which could be a task or subprocess.[Suggest change element to BpmnActivity, since there is an attribute Implementation which means something else entirely.]
BPMN: Identifies XPDL activity as a BPMN event.
Deprecated from XPDL2.0. Must be a child of Performers
BPMN: unique identifier of the flow object
BPMN: label of the flow object in the diagram
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: Corresponds to embedded subprocess. Pointer to ActivitySet/@Id in XPDL.
BPMN: Determines whether the subprocess is rendered as Collapsed or Expanded in diagram. Default is Collapsed.
BPMN (and XPDL??Allows arbitrary grouping of various types of elements, for reporting.)
BPMN and XPDL
Deprecated in XPDL 2.1, now use PageId and Page element
BPMN and XPDL
Activities incur costs in a number of way, the use up
resources which may be people, machines, services, computers,
office space, etc. Activities also use up fixed costs which
may be assigned on an activity by activity basis, thus allowing
for the assignment of overhead. Fixed costs are assigned in bulk,
that is to say there is one fixed cost per activity. However
resource costs are assigned on a resource by resource basis,
each one having a cost and an associated time unit.
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
Deprecated in BPMN1.1
Deprecated in BPMN1.1
BPMN provides a timer event to support this type of functionality and it is the preferred method for doing this.
This name should match that specified in Transition/Condition/Expression
BPMN
Required if the Trigger or Result is Message
BPMN
BPMN: corresponds to a task with unspecified TaskType
BPMN: corresponds to a task with specified TaskType
BPMN: corresponds to Reusable subprocess. May run in different pool or same pool.
BPMN
BPMN
BPMN
BPMN
BPMN: Must be present if if Trigger or ResultType is Compensation.[This event can be attached or throwing. Thus name of element should be TriggerResultCompensation.]
BPMN: Link event connects source and target nodes of the same process or subprocess. Equivalent to a sequence flow between source and target nodes.
BPMN: if the TriggerType is Multiple then this must be present. Only valid for attached event. [EventDetail elements are incorrect. They should be message, timer, error, conditional, signal, cancel.]
Required if the Trigger is Message
BPMN: Presence of attribute indicates attached intermediate event; attribute value points to the BPMN activity (task or subprocess) the event is attached to. Absence of the attribute indicates intermediate event in sequence flow. Pointer to Activity/@Id, where activity type must be a task or subprocess.
BPMN
Deprecated in BPMN1.1
Deprecated in BPMN1.1
Deprecated in BPMN1.1
BPMN
Deprecated from BPMN1.0.
Deprecated from BPMN1.0.
BPMN
Co-ordinates / Sizes are in pixels - this attribute specifies the number of pixels per millimeter used by application.
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
Deprecated in XPDL 2.1, now use PageId and Page element
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
BPMN: Corresponds to BPD identifier. Target of @DiagramRef in Subflow.
A String or Expression designating the Performer
BPMN and XPDL
BPMN
BPMN
BPMN: Pool label in diagram
BPMN: Pointer to WorkflowProcess/@Id; presence indicates this pool is part of an internal (private) process.
BPMN
changes xpdl 1.0 order
BPMN: unique identifier for the process, referenced by Pool
BPMN: label of WorkflowProcess in diagram, should be same as for Pool
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
BPMN: Reference to a BPMN task or subprocess definition elsewhere; should not be used for gateway or event. Pointer to Activity/@Id in XPDL.
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.
Deprecated in BPMN1.1
Deprecated in BPMN1.1
Deprecated in BPMN1.1
Applicable only to XOR Gateways
Deprecated in BPMN1.1
Deprecated in BPMN1.1
Deprecated in BPMN1.1
BPMN
BPMN: Trigger or Result type for the event
Required if the Trigger is Message
BPMN: Corresponds to BPMN attribute ProcessRef, pointer to WorkflowProcess/@Id in BPD referenced by PackageRef. [Suggest name change to ProcessRef; this is IDREF not ID].
BPMN: Detrmines rendering of subprocess as Collapsed or Expended. Default is Collapsed.
BPMN: Corresponds to BPMN attribute DiagramRef, pointer to a BPD identified by Package/@Id. [Maybe IDREF doesn't work here since ID is in a different document.]
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: TaskType = Service. In BPMN generally signifies any automated activity.
BPMN: TaskType = Receive. Waits for a message, then continues. Equivalent to a "catching" message event. In BPMN, "message" generally signifies any signal from outside the process (pool).
BPMN: TaskType = Manual. Used for human tasks other than those accessed via workflow.
BPMN: TaskType = Reference. Task properties defined in referenced activity.
BPMN: TaskType = Script. Used for automated tasks executed by scripts on process engine, to distinguish from automated tasks performed externally (Service).
BPMN: Task Type = Send. Equivalent to a "throwing" message event. Sends a message immediately and continues. In BPMN, "message" signifies any signal sent outside the process (pool).
BPMN: Task Type = User. Generally used for human tasks.
BPMN
BPMN
BPMN: Implementation-related but required by spec.
BPMN: Implementation-related but required by spec.
BPMN
BPMN: Pointer to Activity/@Id that defines the task.
BPMN
BPMN: Implementation-related but required by spec
Required if the Task is Send
BPMN
BPMN: Implementation-related but required by spec.
BPMN: Implementation-related but required by spec.
BPMN: Implementation-related, but 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.
The link can only be used within one process as a shorthand for a long sequence flow .
BPMN: If the Trigger or Result Type is Message then this must be present
Text description of the signal
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. DEprecated in BPMN1.1
This is the nameof a Rule element.
Deprecated in BPMN1.1
BPMN: If the Trigger Type is Timer then this must be present
Deprecated
Deprecated
BPMN: If the Implementation is a WebService this is required.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy