Thanks again, What would happen to the sub process if the parent workflow ends? and what if calling dashboard.wait_for with the wfid? Would that be enough to achieve what I'm looking for? running a workflow regardless of whether the parent workflow ends (it would probably end before the sub process) and i'd like to know when the parent process ends successfully and keep the sub process running...
Perhaps launching the workflow from a participant is more suitable for that case? Idan On Monday, October 21, 2013 10:43:11 AM UTC+3, John Mettraux wrote: > > > On Mon, Oct 21, 2013 at 12:15:26AM -0700, Idan Moyal wrote: > > > > What would you suggest if I need to launch an independent workflow from > my > > "main" workflow? > > AFAIK sub processes are bound to their containing workflow. > > > > I guess I can always write a participant for launching workflows on the > > current engine. > > Hello again, > > yes, you can do that. > > You could also do > > ```ruby > subprocess 'x', :forget => true > ``` > > The subprocess would have the same wfid has the parent process but it > would > be execute on its own. > > ```ruby > subprocess 'x', :new => true > ``` > > Might be interesting. Keeping it for ruote 3.0 > > > Best regards, > > -- > John Mettraux - http://lambda.io/jmettraux > > -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
