osworkflow / docs / Integration_with_Other_Modules.html

<html><head><title>OSWorkflow Integration with Other Modules</title></head><body>
<ul class="star">
<li>Up to <a href="Documentation.html">Documentation</a></li>
<li>Back to <a href="Configuration.html">Configuration</a></li>
<li>Forward to <a href="Workflow_Definition.html">Workflow Definition</a></li>
</ul>
<h3 class="heading-1-1">Integration with OSCore
</h3><p class="paragraph"></p>OSWorkflow requires <span class="nobr"></img><a href="http://www.opensymphony.com/osuser">OSUser</a></span> and <span class="nobr"></img><a href="http://www.opensymphony.com/propertyset">PropertySet</a></span>, which both require <span class="nobr"></img><a href="http://www.opensymphony.com/oscore">OSCore</a></span>. Furthermore, OSWorkflow makes heavy usage of the many useful features in OSCore, and therefore OSCore version 2.0.1 or above is required to use OSWorkflow.
<h3 class="heading-1-1">Integration with PropertySet
</h3><p class="paragraph"></p>One of the key features in OSWorkflow is the ability to save variables dynamically. This allows for a <a href="Functions.html">Functions</a> function to take place on day 1 in the workflow lifecycle and store a piece of data in OSWorkflow. Then, many days later, when an action is executed in the workflow, that same data can be pulled up and re-used in another function. This is a very powerful feature that when used properly can allow for highly customized, long-lived workflow behavior that persists even after server restarts.<p class="paragraph"></p>This is all possible by using the <span class="nobr"></img><a href="http://www.opensymphony.com/propertyset">PropertySet</a></span> module. What kinds of variable types you can dynamically store in the propertyset (usually exposed as the variable <b class="bold">ps</b>) is totally up to the PropertySet implementation that is chosen by the <b class="bold">WorkflowStore</b> you have configured in <b class="bold">osworkflow.xml</b>. For example, if you choose the <b class="bold">JDBCWorkflowStore</b>, you must make sure that the jdbc propertyset is properly configured in <b class="bold">propertyset.xml</b>. Information on setting up the propertyset backend store (for example, sql scripts for the JDBCPropertySet) can be found in the propertyset download.</body></html>
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.