Sub-process Executes First Defined Transition Automatically

darthmaul Oct 29, 2008 9:42 PM

I am using JBPM pageflows, and occasionally I nest them as sub-flows. Each time I use a sub-flow, the first transition automatically executes without my doing anything. By first, I mean the first transition defined vertically in the XML. The button tied to the transition never gets pressed, and the next node in the pageflow pops up in my browser.

I have tried both starting the nested flow with start-page or start-state, and either way the same thing happens.

Here is the call in the parent flow:

   <process-state name="search">
      <sub-process name="searchPageflow"/>
      <transition to="selection"/>
   </process-state>

Any insight into why this happens is much appreciated.

Thanks.

1. Re: Sub-process Executes First Defined Transition Automatically

darthmaul Oct 29, 2008 10:28 PM (in response to darthmaul)
Has anyone found themselves with a pageflow that stands alone but that they also want to nest? I have this situation. Along those lines, I have two questions:

Am I wrong to do this? Is there a more elegant design?

I could have two versions of the pageflow, one beginning with start-state to nest and another beginning with start-page to stand alone. This approach would have a LOT of repetition. Is there a way to mitigate this?

Thanks.
Actions