Bug 1006093 - Dot separated process variable name as Map accessor on Task parameter mapping fails on Import in Designer
Summary: Dot separated process variable name as Map accessor on Task parameter mapping...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5
Version: BRMS 5.3.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Kris Verlaenen
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On: 999425
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-10 02:15 UTC by Toshiya Kobayashi
Modified: 2018-12-03 19:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 999425
Environment:
Last Closed: 2013-11-04 17:13:05 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPM-4102 0 Major Open Dot separated process variable name as Map accessor on Task parameter mapping fails on Import in Designer 2020-06-04 00:52:42 UTC

Description Toshiya Kobayashi 2013-09-10 02:15:23 UTC 
+++ This bug was initially created as a clone of Bug #999425 +++

Description of problem:

Platform BZ for https://issues.jboss.org/browse/JBPM-4102


Steps to Reproduce:
1. Import sample.bpmn attached to JBPM-4102


Actual results:

Throws an Exception and fails to import.

Expected results:

Import the BPMN successfully
Comment 1 JBoss JIRA Server 2013-09-10 03:20:47 UTC 
Toshiya Kobayashi <tkobayas> made a comment on jira JBPM-4102

Attaching sample bpmn.

- I removed 
targetNamespace="http://www.jboss.org/drools" for Designer to be able to accept.
- I removed 'Result Mappings' which causes another error.
Comment 2 Alessandro Lazarotti 2013-11-04 17:12:13 UTC 
Kris comment at Bug 999425:

sourceRef of a data association should be a valid IDREF, so strictly speaking, it can't be something like <sourceRef>myMap.var1</sourceRef>.  A transformation element (which is an expression inside the data association) should be used to store the expression.

So when using BPMN2 (both Designer and Eclipse), currently the user cannot set expressions as source for data associations.  As alternative, scripts should be used to set a variable with the right value and then use a simple data association to map that variable to the data input.

We will have to consider adding support for transformation expressions in the future.
Note You need to log in before you can comment on or make changes to this bug.