On Mon, Feb 07, 2011 at 05:52:10PM -0800, Raphael Simon wrote: > > This definitely fits the bill. I'm looking forward to the filter attribute > as this is probably going to be how we will be mostly using filters (in the > spirit of mapping 'inputs' and 'outputs' to the workitem). I'm thinking the > standalone expression is great to do validation (e.g. at the beginning of > the workflow and all sub-workflows) while the attribute is what to use to do > the mapping for each participant that needs it.
Hello Raphael, sorry for the late reply : the :filter attribute is in. https://github.com/jmettraux/ruote/blob/e5952b53957642b443327761203f949015710398/test/functional/ft_56_filter.rb It only understands filter passed via variables for now (I'll add filter participants) later. Please tell me if it fits your bill and how I could improve it. > I also like the fact that the filter mechanism is easy to use (via > Ruote::Filter) since I'm thinking our participants will use this directly to > validate the incoming workitem (don't know if it's overkill but at some > level this is nicely independent of everything else and could even live in > its own gem, rufus-validate anyone?) +1 for using Ruote::Filter from your participants. rufus-validate : why not, thinking about it, maybe after I release ruote 2.2.0 Cheers, -- John Mettraux - http://jmettraux.wordpress.com -- 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
