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 it's simply calling the reply method of the engine with the workitem. The engine looks at the FlowExpressionId of the workitem to determine to which expression / process instance the workitem belongs. 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 OK, back to ruote-web2. ActiveRecord >= 2.2 is no friend of mine :( Best regards, -- 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 -~----------~----~----~----~------~----~------~--~---
