Hi, I've spent several hours reading docs, blog posts, and examples, but it's conceptually still a long way away. Our app uses state machine- like rules to track the status of various Active Record models. I think ruote is a great fit for this app (it's a document review system--just like the first example process in the docs), but I'm struggling on how to re-write everything as a workflow engine.
Our app has a model that keeps track of most of the workflow. When managers want to see the progress on each document, we query this model's status. Ruote should work fine as a replacement for nearly all the statuses, but once a process is finished, how should we query for documents that are in their final states (either "published" or "rejected")? Do we have to continue to store these states within the model? Or do we keep processes running forever? Another issue is how to keep track of the histories of each process. Should that be done separately? Thank you -- 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
