[
https://jira.jboss.org/jira/browse/JBPM-2492?page=com.atlassian.jira.plug...
]
Tom Baeyens reassigned JBPM-2492:
---------------------------------
Assignee: Joram Barrez (was: Tom Baeyens)
improve task outcomes
---------------------
Key: JBPM-2492
URL:
https://jira.jboss.org/jira/browse/JBPM-2492
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.0.CR1
Reporter: Shekhar Vemuri
Assignee: Joram Barrez
Priority: Minor
Fix For: jBPM 4.3
Original Estimate: 2 days
Remaining Estimate: 2 days
Description is below:
It was decided in a discussion in the forum(referenced in this issue) that we would not
add the additional transition to the list of transitions that are available as part of
completing a task.
Problem:
Is there a particular reason for why GetOutComes does this?
Code:
Set<String> outcomes = new HashSet<String>();
outcomes.add(Task.STATE_COMPLETED);
.. logic to add other transitions specified in the activity.
When the TaskService.getOutComes(long taskDbId) is called with a task id it returns
completed as an entry in the list of Transitions that will eventually be shown to the
user.
But this particular transition is not even being modeled in the process_definition.
There are other places in the code, where in if a transition/outcome name is not
specified then the transition is assumed to the 'completed' and special handling
is done,
Code:
if (Task.STATE_COMPLETED.equals(signalName)) {
if (outgoingTransitions.size()==1) {
transition = outgoingTransitions.get(0);
} else {
transition = activity.getDefaultOutgoingTransition();
}
}
The above snippet is from TaskActivity.
What is the reasoning behind adding this to the transitions that can be taken out of a
Task node?
_________________
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira