Thanks a lot, that's all I needed to know. I'm going to study those articles and stick with AASM.
Best, Lance On Feb 28, 6:33 pm, John Mettraux <[email protected]> wrote: > On Sun, Feb 28, 2010 at 11:26 PM, viatropos <[email protected]> wrote: > > > My question is, is this the kind of thing I'd use Ruote for? Or would > > Stonepath be a better fit? I don't quite understand the difference > > between "Workflow Resource Patterns" vs. "Workflow Control Flow > > Patterns", and "Task Managers" vs. "Workflow Engines", and am not sure > > when I'd need to actually have an operating system of processes going > > vs. just storing states in a database. I'm hoping to make this thing > > as dynamic and modular as possible so I could automate more and more > > of their business as we go. > > Hi again, > > there is no way for me to give you a cheap piece of advice. It all > involves telling you to learn more about this or that. > > I cannot say much about StonePath. You are already using AASM, it > seems sufficient. > > Now the jump from AASM to ruote... I'd honestly say, don't use ruote. > > Your needs seem very basic. Create a model called Task, with a state > field mapped to a user and then define some transitions, the set of > which is your workflow then you're done. I guess that this 1 Task = 1 > Workflow thing is sufficient for you. To cancel/terminate a workflow > simply delete the task. AASM is your friend. > > (In fact, I'd call that model Case instead of Task). > > When your transition handling code becomes scary, come back. > > 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
