On Tue, Jul 30, 2013 at 08:08:02PM -0700, Ravi Gadad wrote:
>
> Prepare yourself for the longest message in the universe!
Hello Ravi,
welcome to the ruote mailing list!
Sorry, if I don't go into the details of your email, but my time is limited
and I prefer a dialog. Respdonding to all the leave questions of your email
would turn your tree of questions into a forest quickly.
This is how I understand your email:
```ruby
Ruote.define do
cursor do
concurrence do
super_admin_batch :task => 'batch review'
concurrence do
admin :task => 'review application'
intern :task => 'collect additional doc'
end
end
rewind :if => '${re_review}'
end
finance :task => 'charge applicant', :if => '${approved}'
end
```
There is an "application" domain object, which goes through an "application
process", well, process.
Applications comes in at any time, admins and interns may lay their hands on
it at any time. While applications are on, they get added to a
"super_admin_batch", which aggregates one workitem per ongoing application
process.
When super_admin, admin and intern have replied (with their workitems), a
rewind happens (or not), if no rewind, the application process is over, it is
eventually charged to the applicant.
Now, what is wrong with my explanation?
Kind 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.
