Hi guys. As you know, I'm rather new to the list and ruote.
I've reviewed a decent amount of the documentation at this point, although I
have to confess I need to back through it as some of it (particularly "How
ruote works") made my head spin a bit. Of course, this was after a few pints
of Guinness, so the docs may not be to blame.
Anyway, I'm planning to use ruote to replace an aging Java-based document
approval system we use here. It's a fairly basic system and currently only
supports two document types. Capexes and PRs. The company plans to expand
document types in the near future, which is one reason for rewriting it,
aside from the fact that it's suffering from severe code rot.
Today, the two flows are such:
1. CAPEX is attached and a manager is selected from a drop down box.
2. CAPEX is routed to that manager's work queue and he/she is notified via
email.
3. Manager approves or disapproves.
- Approve: CAPEX is moved to Role Capex Manager's work queue (4).
- Reject: CAPEX is marked rejected and returned to initiator.
4. If Capex Manager approves, it's moved to CFO's queue. If not, rejection
as above.
5. If CFO approves, it's moved to President's queue. If not, rejection.
6. If President approved, it's marked as completed and initiator is
notified.
7. Complete.
1. PR is attached and a form field is completed with the PR's dollar value.
Manager is selected from drop down box.
2. PR is routed to that manager's work queue and he/she is notified via
email.
3. Manager approves or disapproves.
- Approve: see step 4.
- Reject: PR is marked rejected and returned to initiator.
4. If dollar value is greater than $10000, PR is routed to CFO for approval.
If not, it goes directly to number 6.
5. If CFO approves, capex is routed to Accounting for approval. If not,
rejection as above.
6. If Accounting approves, PR is marked as complete and submitter is
notified. If not, rejection.
7. Complete.
As you can see, these are fairly simple workflows based on responsbilities
assigned by role. We essentially have a many-to-many relationship between
users and roles.
I was hoping someone might give me a helpful push in terms of accomplishing
these sorts of flows in ruote. I suspect an example of doing this will be
just the push I need. I believe based on other threads regarding ruote and
passenger being a no-go, I'm going to attempt this with ruote-rest (unless
JRuby does away with this problem).
Anyway, any examples or advice is greatly appreciated.
Thanks,
JB
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
