On Wed, Mar 4, 2009 at 5:30 AM, J B <[email protected]> wrote:
>
> 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.

Hello again,

I've uploaded something at http://gist.github.com/73813

It explores some variants (like using a subprocess definition, ...)

Questions are welcome.

"attaching" documents to process instances is IMHO a bad thing : we
live in a web/internet world, everything should have a URI (IRI), even
if it's just a path to a document in the forgotten Z: drive or an
identifier in some Lotus Notes drawer. Like, in programmation, we tend
not to copy each value, but we pass pointers, pass the URL to stuff /
documents, let workflow/BPM stuff be independent of the
content/record/document management stuff.


> 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.

Ruote process definitions only know about participants (and
subprocesses), users and roles emerge later (sorry, no convention over
configuration here).


> 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).

If you just need a small departmental workflow engine, MRI with a
single Mongrel might be sufficient.


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
-~----------~----~----~----~------~----~------~--~---

Reply via email to