> On 13-06-19 04:56 PM, [email protected] 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?
> >
> > (...)
> >
> > 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).
>
On Wed, Jun 19, 2013 at 05:11:51PM -0400, Danny Fullerton wrote:
>
> 2. Yes but I'll leave this to John.
Look at the StoreParticipant. The simplest way to do it is to decide that
participant_name == user_name and do things like:
```ruby
Ruote.define do
alice :task => 'prepare doc'
bob :task => 'advise on doc'
charly :task => 'approve / reject'
end
```
Another technique is to use role names as participant names:
```ruby
Ruote.define do
writer
adviser
supervisor
end
```
Yet another technique is to use department names ...
I hope you get the trick.
> > 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).
>
> 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.
Archival / history is left to you. Out of the box, ruote has a some kind of
history component:
https://github.com/jmettraux/ruote/blob/2048bc6ad7/test/functional/ft_36_storage_history.rb
https://github.com/jmettraux/ruote/blob/2048bc6ad7/test/functional/ft_37_default_history.rb
> > 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).
>
> 4. Yes, you should take a look at Ruote-kit which shows the current
> position of a process.
Combining the history above or Danny's AuditTrail plus the Ruote::Dashboard
ProcessStatus (used by ruote-kit) will give you that.
> > 5. Ability to tag process instances and search/query based on those tags.
>
> 5. I'll leave this to John.
It's possible, but not out of the box. It might be not very efficient.
Best regards,
--
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
---
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.
