2009/3/4 J B <[email protected]>: > 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.
Hi John, understood, "how ruote works" is very low-level. > 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. Some kind of a draft : http://gist.github.com/73752 I will answer to the rest of your questions a bit later. Best regards, -- 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 -~----------~----~----~----~------~----~------~--~---
