[
https://jira.jboss.org/browse/JBRULES-2716?page=com.atlassian.jira.plugin...
]
Kris Verlaenen resolved JBRULES-2716.
-------------------------------------
Fix Version/s: 5.2.0.M1
Resolution: Rejected
This is actually expected bahaviour, the name of the work item represents the type of work
that the work item represents. In the case of a user task, this will always be
"Human Task", as it represents the execution of some human task. Note that the
work item has additional properties, like a "TaskName" etc. that contains a lot
of additional information about the work item, and TaskName would probably be the property
you should use to describe the user task in more detail in your case. Other service nodes
can generate work items with a different name, like email nodes, etc. Check out the
chapter on domain-specific work item nodes for more info.
WorkItem getName always returns "Human Task" when using a
bpmn model schema
---------------------------------------------------------------------------
Key: JBRULES-2716
URL:
https://jira.jboss.org/browse/JBRULES-2716
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (flow)
Affects Versions: 5.1.0.FINAL
Environment: java version "1.6.0_21"
Reporter: Simon Bronner
Assignee: Kris Verlaenen
Priority: Minor
Fix For: 5.2.0.M1
Regardless of the Name defined for a userTask in the bpmn, "Human Task" is
always returned on a call to getName() on org.drools.runtime.process.WorkItem
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira