documentation

bits and pieces of documentation.

presentations

• Kenneth Kalmer presented Ruote in 20 minutes at Ruby on Beer in Johannesburg

• Two presentations of Ruote, one from October 2008 and one from June 2008

quickstarts

• simple.rb is a small example, one process definition, two participants

• the ruote quickstart details how to install the ruote and gem and to write a first process definition and then launch a few instances of it

basic documentation

• examples/engine_template.rb is a piece of Ruby code (lots of comments though) instantiating a ruote engine, it details all the common engine configuration switches.

• the ruote engine expects [business] process definitions as a set of expressions.

• there are three ways to write process definitions, as XML, as Ruby or directly as process definition tree.

• the engine communicates with the external world via participants that abstract the ‘who’ or ‘what’ is handling the workitems handed by the engine (to them, participants).

• workitems

• there are various persistence flavours for the engine

advanced documentation

• the glossary enumerates concepts and terms used throughout Ruote and attempts at giving explanations for them

• ruote’s rdoc (raw ruby documentation)

• some notes about process administration

• on_error / on_cancel are two expression attributes used to redirect the flow of a process in case of error or just when it gets cancelled

• a few lines about interaction between engine and participants (local or remote).

• ‘workflow patterns’ provide a conceptual basis for process technology, they are enumerated by the research groups of Prof van der Aalst and Prof ter Hofstede at http://workflowpatterns.com the following documentation piece details how a certain number of control flow patterns can be implemented with Ruote

blog excerpts

a few links to blog posts about ruote.

• how does Ruote work ?