On Thu, Mar 5, 2009 at 10:37 PM, John Mettraux <[email protected]>wrote:
> > On Fri, Mar 6, 2009 at 11:45 AM, J B <[email protected]> wrote: > > > >> Ruote-web2 and ruote-rest do that via an "inbox" mechanism. > > > > So maybe that documentation I ask for above is in fact the code our > > ruote-web2. I was unable to dig into that today, but will tomorrow. > > Hello, > > fetching the workitems (in the inbox) : > > > http://github.com/jmettraux/ruote-web2/blob/2821ab2a002d35a915a126a7d7146c228201d68c/app/controllers/workitems_controller.rb#L39 > > proceeding a workitem : > > > http://github.com/jmettraux/ruote-web2/blob/2821ab2a002d35a915a126a7d7146c228201d68c/app/controllers/workitems_controller.rb#L145-154 > > Cool..thanks for the direct links. OK for the document based workflows, but sometimes it's way easier for > a Rails (or Ruby) person to simply use act_as_a_state_machine (or > 'workflow') and attach states to the document "resource". Else it's > back to commercial [open source] vendor gaming with things like > Alfresco : > http://stackoverflow.com/questions/593123/open-source-document-approval-system-or-framework > So when would it be appropriate to use a state machine versus a workflow engine? Our new system needs to make decisions in a more complex way (i.e., if a field has a value > n, route this way, else route that way...things like that). I'm betting aasm would be a lot simpler, but I'm not sure it's ilk supports these sorts of flows. > OK, back to ruote-web2. ActiveRecord >= 2.2 is no friend of mine :( > Ah, so you've hit problems with rails 2.3 now as well? Thanks again. John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
