On Sun, Nov 07, 2010 at 03:40:06AM -0800, mauro wrote:
>
> First of all sorry for my bad english, I'm italian.
> I'm totally new on workflows and route.
> I want to develop an application to manage computers installation
> processes in my company.
> My framework choice is ruby on rails.
>
> The process is:
> a user interview the computer owner, fill a card and the data is
> passed to the installer which will install the
> computer.
> At the end of the work the installer fill a card and indicate if the
> work is' finished good or not.
>
> Do you think that's good for using route?
> Please some advice.
Hello,
this looks like
Ruote.process_definition 'installation' do
sequence do
clerk :task => 'interview user'
technician :task => 'install computer'
end
end
It could also be implemented by having a Card active record and a field
'status', which can be set to "to be installed", "installed successfully" or
"install failed"...
This makes for two approaches, a declarative workflow vs an implicit workflow
supported by the lifecyle of a business entity (the card).
Ruote is advantageous when you want to have multiple versions of a process
running (and by extension, multiple processes).
This blog post contains (especially in the second paragraph) a hint on the
difference between business process and business entity lifecyle :
http://jmettraux.wordpress.com/2010/10/27/resource-lifecycle-tuple/
There is a sample of an integration of ruote in Rails at :
https://github.com/tosch/ruote-on-rails
Welcome to the ruote mailing list, questions are welcome,
--
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
