[jboss-jira] [JBoss JIRA] (GPD-392) Force a transition to have its name in case of Fork

[Koen Aers (JIRA)]

     [ https://issues.jboss.org/browse/GPD-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koen Aers resolved GPD-392.
---------------------------
    Resolution: Out of Date


> Force a transition to have its name in case of Fork
> ---------------------------------------------------
>
>                 Key: GPD-392
>                 URL: https://issues.jboss.org/browse/GPD-392
>             Project: jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.7, jBPM jPDL Designer 3.2
>            Reporter: Toshiya Kobayashi
>            Assignee: Koen Aers
>
> When you add transitions from a fork to nodes, GPD omits the name of the first transition.
>        <fork name="fork1">
>                <transition to="node1" ></transition>
>                <transition to="node2" name="to node2"></transition>
>                <transition to="node3" name="to node3"></transition>
>        </fork>
> This works without problem. Tokens go to node1, node2, node3.
> But, after some modification, you may have a process definition like:
>        <fork name="fork1">
>                <transition to="node1" name="to node1"></transition>
>                <transition to="node2" ></transition>
>                <transition to="node3" name="to node3"></transition>
>        </fork>
> In this case, tokens go to node1, node1, node3.
> Because if there is a transition without name, the child token goes to default leaving transition (in this case, node1).
> This problem may be fixed on jBPM side, but forcing a transition to have its name on GDP side will help users avoid such odd process definition.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)