I am new to ruote and have a couple of questions about process
administration.
1.) I have a process for an invoice approval workflow that looks like
this:
def invoice_workflow(invoice_id)
Ruote.process_definition :name => 'test',:time_out => '7d' do
cursor do
set :v => "billing_clerk", :value => "me"
set :v => "invoice_id", :value => invoice_id
set :v => "message", :value => "$:r{some_value}"
billing_clerk
set :v => "message", :value => "$:r{some_value}"
set :f => "reason", :value => "This is a great invoice"
biller_reviewer
payer_reviewer
end
:on_error
sequence {admin }
:on_timeout
sequence {admin }
end
My question is how do I manipulate the workflow once it is in process.
Can I or the administrator rewind,jump,skip, or insert directly or
does it have to be hardwired in the process definition? The problem
comes up because the workflow may have adhoc components by any
participant in the chain. They could each either approve, reject or
forward a bill and I am not sure what the best way to express it is.
A couple of examples:
a.) The administrator notices that the payer_reviewer is on vacation
and wants to route the bill to someone else for approval.
b.) The payer_review wants to forward the bill to someone adhoc.
c.) The_payer_review wants to route the bill back to the billing
clerk.
2.) Regarding participants ,I have hundreds of user who fall into
different roles. What is the best practice for creating role based
participants and how should they be represented (user_id,email,etc).
How do you change a workitem in process if I need to change people in
those roles? ( they get hired,fired or transfered)
3.) The docs are a little confusing about using active record to
persist the datastore. Is it still supported? if so is there a sample
for this?
Thanks
Eric smith
--
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
