1. opensymphony
  2. osworkflow


osworkflow / docs / Introduction.html

<html><head><title>OSWorkflow Introduction</title></head><body>
<ul class="star">
<li>Up to <a href="Documentation.html">Documentation</a></li>
<li>Forward to <a href="Requirements.html">Requirements</a></li>
</ul><p class="paragraph"></p>OSWorkflow is very different from most other workflow systems available, both commercially and in the open source world. What makes OSWorkflow different is that it is extremely flexible. This flexibility can be hard to grasp at first, however. In fact, OSWorkflow does not contain graphical user interface components. It is up to the application developer to provide this sort of integration, as well as any integration with existing code and databases. These may seem like problems to someone who is looking for a quick "plug-and-play" workflow solution, but we've found that such a solution never provides enough flexibility to properly fulfill requirements in a full-blown application. <b class="bold">OSWorkflow gives you this flexibility</b>.<p class="paragraph"></p>OSWorkflow can be considered a "low level" workflow implementation. Situations like "loops" and "conditions" that might be represented by a graphical icon in other workflow systems must be "coded" in OSWorkflow. That's not to say that actual code is needed to implement situations like this, but a scripting language must be employed to specify these conditions. It is not expected that a non-technical user modify workflow. We've found that although some systems provide GUIs that allow for simple editing of workflows, the applications surrounding the workflow usually end up damaged when changes like these are made. We believe it is best for these changes to be made by a developer who is aware of each change. Having said that, the latest version provides a GUI designer that can help with the editing of the workflow.<p class="paragraph"></p>OSWorkflow is based heavily on the concept of the <b class="bold">finite state machine</b>. Each state in represented by the combination of a step ID and a status. A <b class="bold">transition</b> from one state to another cannot happen without an action occuring first. There are always at least one or more active states during the lifetime of a workflow. These simple concepts are what lie at the core of the OSWorkflow engine and allow a simple XML file to be translated in to business workflow processes.</body></html>