• XPDL 2.1 Proposals

Test Run/Simulation values for the DataMapping tags

|Please note: this is a preliminary proposal for XPDL 2.1 which has not yet been adopted by the coalition. Please use this page for discussion of that proposed extension. This proposal may change substantially before adoption, or may possibly never be officially adopted in this form.

• Tags:

The new tag would be called TestValue.

<xsd:element name="TestValue" type="xpdl:ExpressionType"/>

• Context:

The new tag would be added as a subtag to DataMapping changing the whole definition to:

<xsd:element name="DataMapping">
    <xsd:annotation>
        <xsd:documentation>XPDL and BPMN:Maps fields between calling and called processes or subprocesses</xsd:documentation>
    </xsd:annotation>
    <xsd:complexType>
        <xsd:sequence>
            <xsd:element name="Actual" type="xpdl:ExpressionType"/>
>>>change
            <xsd:element name="TestValue" type="xpdl:ExpressionType" minOccurs="0"/>
<<<change
            <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
        </xsd:sequence>
    <xsd:attribute name="Formal" type="xsd:string" use="required"/>
    <xsd:attribute name="Direction" default="IN">
        <xsd:simpleType>
             <xsd:restriction base="xsd:NMTOKEN">
                 <xsd:enumeration value="IN"/>
                 <xsd:enumeration value="OUT"/>
                 <xsd:enumeration value="INOUT"/>
             </xsd:restriction>
        </xsd:simpleType>
    </xsd:attribute>
    <xsd:anyAttribute namespace="##other" processContents="lax"/>
    </xsd:complexType>
</xsd:element>

• Description:

The purpose of adding this tag is to make it possible to enter test run or simulation values. This would enable the process engine to fake the call to the subprocess/application. Instead of making the call to application/sub process, an engine could just pass the specified test values as a return to the parent process, as if the call has really happened. The TestValue tag would be allowed only for the OUT and INOUT directed mappings.

An example:

<DataMappings>
.....
    <DataMapping Formal="subprocParam1" Direction="OUT">
        <Actual>ParProcFieldName</Actual>
        <TestValue>'This subprocess has not been invoked'</TestValue>
    </DataMapping>
.....
</DataMappings>