On Sat, May 05, 2012 at 06:20:49PM -0700, Damon Torgerson wrote: > > Given the ruote and process experience on this list, I was wondering what > your thoughts are on when you might combine a state machine with ruote. In > the simple example above, would adding state to the form simply be > redundant? What other considerations should I...consider?
Hey guys, feel free to answer to this thread, we all faced this at some point. Please help Damon. OK, personally, I like to use quaderno http://jmettraux.wordpress.com/2010/09/22/quaderno/ to do forms with ruote. With or without using quaderno, I tend to have a matrix process/user/task to decide which form to present to a user given a workitem and the process it belongs to. It looks like a routing system. Now your idea of having separate forms and form data as resources sure sound good. If you need to enforce some behaviours on state change, then, yes, a state machine might come in handy. Using a workflow engine is orchestrating resources. Using state machines is choreographing resources. Both can be used together, there are pluses and minuses on both sides. There is state without state machines. Workflows and state machines break or go out of sync, resources stay and the show must go on. If the data stays in the form then it's probably better not to duplicate this data in the workitem. A reference/link to the form is sufficient. Not sure if this answer will help, I hope others will chime in. Cheers, -- John Mettraux - http://lambda.io/jmettraux -- 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
