Hi Danny, Thanks for the quick reply. The support on this mailing list has been fantastic so far.
Regarding your Audit Trail observer, is this something you are developing with plans to release to the community? If we decide to go with ruote (and that is looking likely), I would be willing to help you with this, since this is something we'll need as well (assuming your vision of Audit Trail observer line up with our needs). Best Regards, Denis On Wednesday, June 19, 2013 4:11:51 PM UTC-5, Danny Fullerton wrote: > > Hello Denis, > > Welcome to Ruote's mailing list. > > I'll try to answer to the best of my knowledge but John will be able to > complete if necessary. > > 1. Yes, I seen some discussion on the mailing list about this. You should > take a look at re_apply and the test cases ( > http://ruote.rubyforge.org/process_administration.html#re_applying). > > 2. Yes but I'll leave this to John. > > 3. The moment a process is completed it gets erased. I believe the Audit > Trail observer I'm working on (or your own implementation) should be able > to answer this. Basically, once completed, the entire process tree and > applied workitems gets saved iin an archive. > > 4. Yes, you should take a look at Ruote-kit which shows the current > position of a process. > > 5. I'll leave this to John. > > regards, > > -- > Danny Fullerton > Founder > Mantor Organization > > On 13-06-19 04:56 PM, [email protected] <javascript:> wrote: > > Hi, > > We are currently evaluating ruote against a set of requirements we came up > with that a prospective workflow engine solution must meet. So far ruote > is stacking up pretty well against our requirements, but we have a few > requirements that I am trying to figure out how we would satisfy them > either using ruote out-of-the-box, or via some code we write that sits on > top/alongside of ruote. > > Can ruote do the following things, and if so, how? > > 1. Ability for an admin to set the current step/expression of a process > instance (and then resume). Here's the use case: something is broken in > production that needs to be fixed, so pause the process instance, deploy a > fix, and then resume the process at a specific step/expression. > > 2. Ability to assign a step in a process to a user, and to be able to show > the user the steps assigned to him that currently require action on his > part (i.e. steps in running processes that are waiting for a reply to > continue). > > 3. Ability to query for completed process instances (e.g. get a list of > all the processes that ran between 6/1/2013 and 6/15/2013). > > 4. Ability to query for the execution history of a process instance (i.e. > be able to see what part of a process has been executed and where the > process is currently at). > > 5. Ability to tag process instances and search/query based on those tags. > > I realize that I may not be providing enough context to make those > requirements clear, so please let me know if something is unclear and I > will try to explain our needs better. > > Thanks, > Denis > > -- > -- > you received this message because you are subscribed to the "ruote users" > group. > to post : send email to [email protected] <javascript:> > to unsubscribe : send email to [email protected]<javascript:> > more options : http://groups.google.com/group/openwferu-users?hl=en > --- > You received this message because you are subscribed to the Google Groups > "ruote" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- -- 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 --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
