Thanks for the quick reply.  That did the trick.  Didn't realize you could
pass options to concurrence.

One other question.  Is there a way to access the history of a workflow
process. I saw Ruote::StorageHistory but not quite sure if that will work.
 If on the previous example I append the two lines

history = dashboard.context.history.by_process(wfid)
> history.each{|h| puts h["participant_name"]}



I get the following


> print_messages
> print_messages
> con2
> con2
> con1
> con1
>
>
> con1
> con2
>
>
>
> print_messages
>

It looks like the execution path through ruote, but includes lines such as
concurrence (blank line - no participant name).  Looking more for a result
like %w{con1 con2 print_messages}

Thanks for your work on Ruote.

Doug


On Thu, Mar 22, 2012 at 2:57 PM, John Mettraux <[email protected]> wrote:

>
> On Thu, Mar 22, 2012 at 09:06:45AM -0700, Doug Bryant wrote:
> >
> > Am I missing something about how the concurrence block works or is this
> the
> > expected behavior?
>
> Hello Doug,
>
> welcome to the ruote mailing list.
>
> This is the expected behaviour. You can obtain the behaviour you wanted by
> setting the :merge_type attribute to "mix", as in:
>
> ---8<---
>  concurrence :mt => 'mix' do
>    con1
>    con2
>  end
> --->8---
>
> The :merge and :merge_type attributes are detailed in the concurrence
> documentation:
>
>  http://ruote.rubyforge.org/exp/concurrence.html
>
>
> Best regards,
>
> --
> John Mettraux - http://lambda.io/processi
>
> --
> 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 "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

Reply via email to