[
https://jira.jboss.org/browse/JBPM-2920?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu commented on JBPM-2920:
-----------------------------------
Just consider about this. Should we let joinActivity auto-detect when process instance
should continue. Just like InclusiveGatewayActivity in BPMN2.
Now, JoinActivity used incoming transitions number to decide when process instance should
continue. if the actual number of children executions is not equals as incoming
transitions, we should set the multiplicity attribute to let JoinActiivty know when
should continue.
But if we want to support N of M paths in forkActivity, should we ask people to set
multiplicity for each time?
Choose N tasks out from M paths in fork nodes
----------------------------------------------
Key: JBPM-2920
URL:
https://jira.jboss.org/browse/JBPM-2920
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4
Environment: JBOSS 5.1GA, JBPM 4.4,
Reporter: Jecoso Chou
Assignee: Maciej Swiderski
Fix For: jBPM 4.5
Attachments: JBPM-2920.patch
For example:
<fork name="fork1">
<transition name="to A" to="A">
</transition>
<transition name="to B" to="B">
</transition>
<transition name="to C" to="C">
</transition>
<transition name="to D" to="D">
</transition>
</fork>
This issue means that when process to this fork, only some of this 4 transition can be
chosen to go,
for example ,the transition "to A" and "to A".
--
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