+++ This bug was initially created as a clone of Bug #1216108 +++

Description of problem:

If you define Content input variable for REST Task and then use it in Assignment section - it will NOT be preserved.
Version-Release number of selected component (if applicable):
bpms 6.1.0

How reproducible:
always

Steps to Reproduce:
1. create following process:
START->REST TASK->END
2. add Data Input "Content" - String
3. Add Input Assignment  - Content is equal to "whatever"
4. Save and Refresh
5. Content assignment is NOT present anymore

Actual results:
Content assignment in REST Task is not preserved.

Expected results:
Content assignment in REST Task is preserved.


Additional info:

--- Additional comment from Anton Giertli on 2015-04-28 09:57:42 EDT ---

random thought:

Content attribute is already part of the Human Task. 

Coincidence? I think not! 

No, seriously, I am not sure if this is related, but can't think of anything else why would this exact data input name would cause issues.

--- Additional comment from JBoss Product and Program Management on 2015-04-28 10:00:06 EDT ---

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Anton Giertli on 2015-04-29 05:12:35 EDT ---

As discussed with Marek, the reason for high severity is that this issue is making Rest Work Item unusable for POST and PUT methods  since they require Content attribute to be present.

--- Additional comment from Tihomir Surdilovic on 2015-04-29 13:13:00 EDT ---

Fix in master commit : https://github.com/droolsjbpm/jbpm-designer/commit/980ea2203

Some core properties of Task Types such as Comment, Priority, Content, Locale, CreatedBy, etc have their own input editors. For them Designer chooses not to include them in the Assignments property however does create the proper data inputs/assignments for them in the bpmn2. The same was carried over for custom tasks which is the cause of this issue. The error applied to any custom task, not just rest (you can reproduce the same with default Email task for example).

Fixed in master. For custom tasks only TaskName will be treated as independent property.