[
http://jira.jboss.com/jira/browse/JBPM-808?page=comments#action_12349362 ]
Ronald van Kuijk commented on JBPM-808:
---------------------------------------
hmmm... someone care to explain this? Why not use a decision node for this and not go into
the tasknode at all...? Now the designer has to be extended to show this condition as
well.... I'm not saying that I'm against this, but do not see the advantage
immediately, unless it is for ad-hoc tasks that are not part of a process.
Conditional tasks
-----------------
Key: JBPM-808
URL:
http://jira.jboss.com/jira/browse/JBPM-808
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Reporter: Gavin King
Assigned To: Tom Baeyens
Fix For: jBPM 3.2 beta 1
Sometimes you want to be able to create tasks conditionally, ie:
<task-node>
<task name="....">
...
</task>
<task name="approve" if="#{order.total>1000}">
...
</task>
</task-node>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira