Details
Description
User should be able to define the language that an expression is written in DataIO Assignments (just like is supported in Gateways/Sequence Flows).
The possible values should be:
- mvel (marshalled to language= "http://www.mvel.org/2.0")
- Xpath (marshalled to language="http://www.w3.org/1999/XPath")
Example:
<bpmn2:dataInputAssociation> <bpmn2:targetRef>_F0B540FC-711A-4DCB-8DED-D60D67A26409_myTaskVarInputX</bpmn2:targetRef> <bpmn2:assignment> <bpmn2:from xsi:type="bpmn2:tFormalExpression" language="http://www.mvel.org/2.0"><![CDATA[#{my.expression}]]></bpmn2:from> <bpmn2:to xsi:type="bpmn2:tFormalExpression"><![CDATA[_F0B540FC-711A-4DCB-8DED-D60D67A26409_myTaskVarInputX]]></bpmn2:to> </bpmn2:assignment> </bpmn2:dataInputAssociation>
If no language is selected, the language attribute should be omitted in the xml file (just like today) .
Acceptance Criteria
- When selecting the option Expression, in the DataIO Assighments popup, it will display a new selector (TBD: or a button that displays the selection once clicking) which allows to select the language, by providing options:
-
-
- mvel (default value)
- xpath
- Notice NO validation for expression value will be performed during the authoring
-
- The language attribute must be also serialized into the resuling BPMN