Hi again, Allow me to get back to authorization in ruote-rest. AFAIK, 'InFlowWorkItem' has an attribute called 'store'. In ruote-web2, this is a useful way to managing workitems associated to active store participants (delegate, pick).
In ruote-rest, could I use a vanilla active participant with different activities associated to one or several stores? merci bien, Gonzalo On Feb 6, 1:50 pm, John Mettraux <[email protected]> wrote: > On Fri, Feb 6, 2009 at 7:51 PM, Gonzalo <[email protected]> wrote: > > > First of all, I'm very new to ruote-rest and workflows. Any workflow > > is made up of several activities which are arranged in order to fit a > > business process. Is then the term activity and participant (ruote > > term) interchangeable? > > Hi Gonzalo, > > well, for the ruote engine, there are no activities, just participants. > > One convention is to label a participant with an 'activity' attribute, like in > > <participant ref="supervisor" activity="last check" /> > > or > > <supervisor activity="last check" /> > > The workitem the supervisor participant will receive will contain a > field "params" that look like { 'activity' => 'last check' } > > > On the other hand... activities proceeding > > (activity continuation), like filling a form or validating it may > > require some king of authentication... How can this be achived best > > with ruote-rest? > > There is no fine-grained authentication integrated in ruote-rest. It > was thought as a "back office" service. Applications using it are > meant to do the authentication / authorization by themselves. > Ruote-web2 has authentication and authorization. > > Kenneth Kalmer implemented some authentication for ruote-rest. It is > visible in conf/authentication.yaml > > > Is it best to load the workitem payload with read- > > only attributes managing permissions for that workitem? What other > > alternatives could be implemented? > > There is a "filter" mechanism that could interest you : > > http://openwferu.rubyforge.org/expressions.html#exp_filter_definitionhttp://openwferu.rubyforge.org/expressions.html#exp_filter > > It's a way of ensuring that some fields are not modified/visible by > participants. It's not much used, the form handling logic being > usually kept away from the engine (inside of the participants). > > I wrote recently about that in > :http://groups.google.com/group/openwferu-users/browse_frm/thread/f7d3... > > Your idea of attributes for managing permissions makes sense. > > Best regards, > > -- > John Mettraux - http://jmettraux.wordpress.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruote (OpenWFEru) users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
