osworkflow / docs / 3.4 Functions.html

        <title>3.4 Functions</title>
	    <link rel="stylesheet" href="styles/site.css" type="text/css" />

	    <table class="pagecontent" border="0" cellpadding="0" cellspacing="0" width="100%" bgcolor="#ffffff">
			    <td valign="top" class="pagebody">

				    <ul class="star">
<li> Back to <a href="3.3 Common and Global Actions.html">3.3 Common and Global Actions</a></li>
<li> Forward to <a href="3.4.1 Java-based Functions.html">3.4.1 Java-based Functions</a></li>
Functions in OSWorkflow are where you can perform the &quot;meat&quot; of your workflow-based application. They can be executed before and after (pre- and post-) transitions from one state to another in the finite state machine. OSWorkflow supports the following forms of functions:<p class="paragraph"><h3 class="heading3"> <a href="3.4.1 Java-based Functions.html">3.4.1 Java-based Functions</a></h3>
<ul class="star">
<li> Java classes loaded by a ClassLoader</li>
<li> Java classes retrieved via JNDI</li>
<li> Remote EJBs</li>
<li> Local EJBs</li>
<h3 class="heading3"> <a href="3.4.2 BeanShell Functions.html">3.4.2 BeanShell Functions</a> </h3></p><h3 class="heading3"> <a href="3.4.3 BSF Functions.html">3.4.3 BSF Functions</a> (perlscript, vbscript, javascript) </h3><p class="paragraph"><h3 class="heading3"> <a href="3.4.4 Utility Functions.html">3.4.4 Utility Functions</a></h3></p>OSWorkflow also includes a small set of <a href="3.4.4 Utility Functions.html">3.4.4 Utility Functions</a> that will start you off in the right direction. Some of these utility functions are extremely valuable in creating dynamic workflow definitions.