Stefano Cancedda [http://community.jboss.org/people/festano1] created the discussion "Re: Signal a wait state and suspend related running subprocesses" To view the discussion, visit: http://community.jboss.org/message/564261#564261 -------------------------------------------------------------- Thank you for answering, Michael Yes, it's true, but no way to resume the activity on "inactive-scope" and then signal the main instance? My problem is that I *cannot signal the main process*, either if sub-process is "+active-root+" or "+suspended+", etc: INFO  ProcessServiceBean - SUB_PROCESS STATE: SubProcessRequisitesEvaluation.340002 active-root 0.0.1. EXCEPTION ########################################### 12:00:32,886 INF | DefaultCommandService exception while executing command org.jbpm.pvm.internal.cmd.SignalCmd@34e1d5 org.jbpm.api.JbpmException: execution[MainProcess.50026] has running subprocess: execution[SubProcessRequisitesEvaluation.340002] in state active-root So "root execution" cannot be changed whatever state  are their relative "sub-executions"! You talk about a "wait state", but my suspension is acting like a wait state, and i have provided a timer to fire after a timeout, to "resume" process-execution, the problem is *to move* the whole workflow instance to that state. For now I cannot achieve this if sub-process is running, and the solution cannot be to force ending because the sub-process will be locked anyway. I have completely freedom for implemention  but my stand points are: 1. use sub-processes & choose the definition in runtime; 2. enforce the suspension in the root-process; -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/564261#564261] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Stefano Cancedda [http://community.jboss.org/people/festano1] created the discussion "Re: Signal a wait state and suspend related running subprocesses" To view the discussion, visit: http://community.jboss.org/message/564301#564301 -------------------------------------------------------------- OK, but for me is +desiderable+ to suspend execution of the SUB-PROCESS: what I need is to transition the root-process to a "SUSPEND" state (please, see the image at the begin of the original post). Perhaps If execution suspension is not the solution this is not a big problem for me (this reasoning was born because the pvm forbid me to signal the main process that contains the wait state, so i was trying to suspend the sub-process and see what would happen! :) ). Your idea is somewhat vague for me, maybe I don't understand the concept of wait state as you intend it, but: if every signal in the main-process execution, outside the sub-process nodes  will cause an *exception* (until the sub-process instance is ended, of course , +how we can "move to a wait state"+? you intend a fork before entering any sub-process node? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/564301#564301] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]