John, Yes you got my mind. It is exactly that. Of course I have to hack this to adapt to my need. But the less I saw in Ruote is very elegant and seems quite opened to adapt.
Thank you John for the good work. Cordially, Brice On Jan 13, 5:41 pm, John Mettraux <[email protected]> wrote: > On Thu, Jan 13, 2011 at 08:32:16AM -0800, Brice wrote: > > > Thank you very much for your rapid response. > > I am new in this forum and I am sorry not to be clear. > > > In fact, the feature I need is the ability "at the execution time and > > not at the design time" to trace the route and to display where is the > > current step of the workflow. Depending on the state of the task , we > > could have for example : Task to do ( in Red), Pending Task ( in > > Orange) and Task done ( in Green), for example. > > Hello Brice, > > hello Sean, welcome on ruote's mailing list as well, > > ruote, out of the box, is very simplistic. I guess I could equate your three > descriptions as > > * task to do : participant expression not yet reached by flow > * pending task : flow reached participant, workitem pending action > * task done : participant expression was left by flow > > Now you probably have different definitions for this but maybe it's more > worklist related, > > * task to do : workitem reached participant, but no user picked it up yet > * pending task : user picked up / reserved task > * task done : task left user/participant and is [somehow] archived > > Different things for different people. > > Ruote doesn't make too many choices for you. It's swimming in Ruby and a good > Ruby dev can hack a worklist / a set of participants in Ruby for ruote very > quickly, tests included. > > Please feel free to ask any question, cheers, > > -- > 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
