Source

osworkflow / docs / Documentation.html

<html>
    <head>
        <title>OSWorkflow - 
        Documentation
         </title>
	    <link rel="stylesheet" href="styles/site.css" type="text/css" />
        <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>

    <body>
	    <table class="pagecontent" border="0" cellpadding="0" cellspacing="0" width="100%" bgcolor="#ffffff">
		    <tr>
			    <td valign="top" class="pagebody">
				    <p>OSWorkflow is fairly 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 can be hard to grasp at first, however. For example, OSWorkflow does not mandate a graphical tool for developing workflows, and the recommended approach is to write the xml workflow descriptors 'by hand'. 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 all requirements in a full-blown application. </p>

<p><b>OSWorkflow gives you this flexibility</b>.</p>

<p><b>Documentation:</b></p>
<ul>
	<li><a href="Tutorial.html" title="Tutorial">Tutorial</a> - The OSWorkflow tutorial</li>
	<li><a href="Manual.html" title="Manual">Manual</a> - The OSWorkflow documentation</li>
	<li><a href="http://www.opensymphony.com/osworkflow/api" title="Visit page outside Confluence">API JavaDocs</a></li>
</ul>


                    			    </td>
		    </tr>
	    </table>
    </body>
</html>