What is new in XPDL Robert Shapiro VP Global 360 XPDL 2.2 and 3.0 Editor BPMN 2.0 FTF Member Denis Gagné, CEO & CTO Trisotech XPDL 2.2 and 3.0 Co-Editor BPMN 2.0 FTF Member

Our Focus for this session

What is BPMN? Business Process Model and Notation Why BPMN matters? Readily understandable by business stakeholders Aim to bridge the gap from modeling to subsequent implementation

What is XPDL? XML Process Definition Language Why XPDL matters? Meant for interchange from inception Internal model of many existing BPM tools Backward compatibility of BPMN 1.2

BPMI Standards Timeline - Releases WPDL XML BPMN 1.0 XPDL 2.0 XPDL XPDL 1.0 BPMN 1.0 BPMN 1.1 BPMN 2.0 XPDL XPDL 3.0 BPMN 1.2 BPMN R. Shapiro, WfMC

New in BPMN 2.0 Some new concepts and constructs A graphical notation for modeling interactions (adding choreographies and conversations) Better standard conformance specification along with conformance sub-classes A meta-model and accompanying interchange formats both XMI and XSD based A diagram definition model and accompanying interchange formats both XMI and XSD based An explicit execution semantics A mapping from a BPMN subset to WS-BPEL

Modeling in BPMN How to create useful models How to write proper BPMN To do modeling in BPMN at least portions of two bodies of knowledge are required

“ A Model Ultimate Property: Usefulness The World ? Mental Model The Model The Future Purpose & Context Useful Predictions Confirmation Measurements Modeling All models are wrong some are useful

Expressiveness of Intent A wide collection of constructs are available in BPMN allowing: Diagramming to communicate or Modeling for execution Capturing Internal Processes or Collaborations with Partners Use limited vocabulary according to purpose and context Sub classing the language Official Sub Classes: Conformance sub classes of the spec Organization Sub Classes: Modeling Guidelines

BPMN 2.0 by the Numbers 336 Possible Depiction Permutations just for tasks A wide collection of constructs are available in BPMN given its duality with respect to diagramming to communicate or modeling for execution

BPMN’s Devils Quadrant ProcessCollaboration Communication Execution In BPMN It is possible to model the same process in many different ways Each model or diagram may be quite adequate for the intended purpose but simply incorrect for other purposes

Scope of XPDL 2.2 The XPDL 2.2 effort is focused on only covering a subset of the Process Modeling Conformance class of the BPMN 2.0 specification. Thus the XPDL 2.2 schema will offer a serialization and interchange transport for BPMN 2.0: Process Diagrams, and Collaboration Diagrams (Without Conversation) (i.e. what was possible in BPMN 1.2)

Scope of XPDL 3.0 The XPDL 3.0 effort is focused on covering the complete BPMN 2.0 specification. Thus the XPDL 3.0 schema will offer a serialization and interchange transport for BPMN 2.0: Process Diagrams, Collaboration Diagrams, Conversation Diagrams, Choreography Diagrams And all attributes.

What is new in XPDL 2.2? Denis Gagné, Trisotech BPMN 2.0 FTF Member XPDL 2.2 and 3.0 Co-Editor

Goal of XPDL 2.2. The XPDL 2.2 schema is to be backward compatible with the XPDL 2.0 and XPDL 2.1 schemas. This backward compatibility also extends to XPDL 2.1 schema’s capability to serialize BPMN 1.2 drawings.

Guidelines The following guidelines were followed in the production of the new XPDL 2.2 Schema: Where possible elements and attributes of the BPMN 2.0 specification were mapped to semantically equivalent existing elements of the current XPDL 2.1 schema. A concerted effort was made to only introduce new elements and attributes only when absolutely necessary. These new elements and attributes were introduced in a manner coherent with the existing XPDL Meta-model. Care was taken when strongly typing elements and attributes in the XPDL 2.2 schema as some structural rules are divergent or contradictive between BPMN 1.2 and BPMN 2.0. Annotations were inserted in the schema where appropriate to ease readability and clarify mapping intentions ( care was taken in specifying structural conformance rules in annotations, as some structural rules are divergent or contradictive between BPMN 1.2 and BPMN 2.0)

Baseline References XPDL The version bpmnxpdl_33 of the XPDL schema was the baseline for the creation of the XPDL 2.2 schema. BPMN 2.0 Schema The various schema files produced out of Beta 2 of the BPMN 2.0 specification were the baseline for the creation of the XPDL 2.2 schema. BPMN 2.0 Specification Document Version Beta 2 of the BPMN 2.0 specification was the reference for the creation of the XPDL 2.2 schema.

Corrections to XPDL 2.1 Added an Orientation attribute to Lane element. Added Associations and Artifacts as possible children of ActivitySet. Annotated as deprecated LoopCondition attribute in LoopStandard (seems to have been the intent in XPDL 2.1) Annotated as deprecated ComplexMI_FlowCondition attribute in LoopMultiInstance as per XPDL 2.1 Spec document. In LoopMultiInstance, annotated as deprecated MI_Condition attribute. ( Should use the MI_Condition element. This way, when the integer value is known the expression is simply the integer value.) Added a default value of false to IsForCompensation attribute of the Activity Element Minor edits to various annotations of the Route element Re-ordered the enumeration of GatewayType to group deprecated values together Changed the attribute result of EndEvent to required (to align with the trigger for both start and intermediate event which are required) TriggerIntermediateMultiple (for multiple intermediate event) Added TriggerResultCancel element as a possible child node (was missing) EndEvent Added TriggerResultCancel element as a possible child node (was missing) ResultMultiple (for multiple end event) Added TriggerResultCancel element as a possible child node (was missing) Added TriggerResultCompensation element as a possible child node (was missing)

Package Definition Meta Model

Package

Process Definition Meta Model

ActivitySet

WorkflowProcess

Package Definition Meta Model

DataStore Added the DataStore element to capture BPMN 2.0 dataStore. Added DataStores element to Package in order to define the datastore at the package level.

DataStore(s)

Process Definition Meta Model

DataStoreReference Added the DataStoreReference to capture the BPMN 2.0 dataStoreReference. Added the DataStoreReferences element to contain the various DataStoreReference. Added DataStoreReferences element to ProcessType and ActivitySet in order to capture the visual depiction of a DataStore captured at the package level.

DataStoreReference(s)

Package Definition Meta Model

GlobalActivity Added a GlobalActivities element which is a list of activities that are callable, these have to be BPMN 2.0 GlobalTasks Created a GlobalActivityReference element to receive the referenced globalTask of a callActivity (When the callActivity points to a global Process, the SubFlow is used)

CallActivity

GlobalActivity(s)

GlobalTask(s)

GlobalActivityReference

Process Definition Meta Model

Event Sub Process Added an attribute TriggeredByEvent to the ActivitySet element. Added annotation that for a sub process triggered by events the default start activity should be specified (the field already existed)

Event Sub Process

Process Definition Meta Model

Data Modeling Non Visible Target (get target from BPMNDI) Non Visible Source (get source from BPMNDI) Actual Parameter Formal Parameter

DataAssociation(s) Added DataObjects and DataAssociations elements to ProcessType and to ActivitySet in order to capture DataObjects as flow element as per BPMN 2.0. Added DataAssociation element to capture BPMN 2.0 dataAssociation Added DataAssociations element to contain the various DataAssociation

DataAsssociation

DataAssociation(s)

Process Definition Meta Model

DataObject DataObjectReference Added a DataObjects element to contain the various DataObject that were previously contained in artefacts In the DataObject element, added the Object element to support the documentation attribute.

DataObject(s)

Process DataInput DataOuput Added DataInputOutputs as a possible child of ProcessType type. Added DataInput and DataOutput elements to depict Process DataInput and DataOutput

Activity DataInput DataOuput

DataInput / DataOutput

Package Definition Meta Model

Process Definition Meta Model

Current Status of XPDL 2.2 Completed The XPDL 2.2 schema is completed and has been validated and tested. Remaining The XPDL 2.2 Specification Document has been initiated (based on bpmnxpdl_39) Current Schema Version bpmnxpdl_40

Current Status XPDL 3.0 Completed The XPDL 3.0 schema covering all visual elements has been completed and validated Remaining Non visual attributes inclusion has started but is not completed The XPDL 3.0 Specification Document has not been started Current Schema Version bpmnxpdl_41

Call to Action Immediate help is required to complete changes to the XPDL Specification Document to reflect the latest Schema

Business Process Incubator