On Sun, May 06, 2012 at 09:30:00AM -0700, Damon Torgerson wrote:
>
> On Saturday, May 5, 2012 6:47:04 PM UTC-7, John Mettraux wrote:
> >
> > On Sat, May 05, 2012 at 06:20:49PM -0700, Damon Torgerson wrote:
> >
> > 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.
>
> Quademo looks interesting and relevant for me. How/where do you persist the
> form data?
Well, most of the time, in the workitem itself.
Ah, a note about the form / routing system (no quaderno involved) in a Rails
context, it follows this schema usually:
app/views/forms/_{task_name}.haml
app/views/forms/{participant_name}_{task_name}.haml
app/views/forms/{participant_name}.haml
app/views/forms/default.haml
where default.haml is the default form (only development mode) it's used when
there is no specific form for a participant name / task name pair.
> > 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.
>
> Orchestrating vs choreographing is an interesting metaphor that I've seen a
> bit in the process community. For a simple sequential process, then it
> appears to me that the line between ruote and a state machine might get
> blurry.
If you only have sequentials processes and enact them by having a Process
resource and a [different] state machine for each instance of it, then yes,
it's very blurry.
http://www.engineyard.com/blog/2011/ruote-and-flow/
Of course, I may be [very] wrong. Ruote is just routing workitems among
participants, for the rest, please be creative.
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
