-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
False
-
Undefined
-
BAPL-1727 introduces MVEL expressions to update a specific field of a process variable.
The current BPMN Editor let the user define a free expression like in the following Screenshot:
Output data assignment
The BPMN output is:
<bpmn2:dataOutputAssociation> <bpmn2:sourceRef>_24F9FADA-068E-4194-8B94-B523520CFDFF_aOutputX</bpmn2:sourceRef> <bpmn2:assignment> <bpmn2:from xsi:type="bpmn2:tFormalExpression"><![CDATA[_24F9FADA-068E-4194-8B94-B523520CFDFF_aOutputX]]></bpmn2:from> <bpmn2:to xsi:type="bpmn2:tFormalExpression"><![CDATA[#{test.prop}]]></bpmn2:to> </bpmn2:assignment> </bpmn2:dataOutputAssociation>
According the following comment it's wrong from BPMN spec perspective:
This is the desired outcome:
<bpmn2:dataOutputAssociation> <bpmn2:sourceRef>_24F9FADA-068E-4194-8B94-B523520CFDFF_aOutputX</bpmn2:sourceRef> <bpmn2:targetRef>test</bpmn2:targetRef> <bpmn2:assignment> <bpmn2:from xsi:type="bpmn2:tFormalExpression"><![CDATA[_24F9FADA-068E-4194-8B94-B523520CFDFF_aOutputX]]></bpmn2:from> <bpmn2:to xsi:type="bpmn2:tFormalExpression"><![CDATA[#{test.prop}]]></bpmn2:to> </bpmn2:assignment> </bpmn2:dataOutputAssociation>
From a user perspective a desirable behavior could be:
- From drop down select mapping expression
- A new drop down list let the user select the variable
- A new input box let the user fill in the mapping expression this.prop
TO BE EVALUATED Does is makes sense to ask the user to pre-pend #{ and post-pend }?
- is incorporated by
-
RHPAM-3849 No TargetRef when using expressions in DataInput/Output in Assignments
- Closed
-
JBPM-9856 No TargetRef when using expressions in DataInput/Output in Assignments
- Open