Book Image

OSWorkflow: A guide for Java developers and architects to integrating open-source Business Process Management

Book Image

OSWorkflow: A guide for Java developers and architects to integrating open-source Business Process Management

Overview of this book

OSWorkflow is an open-source workflow engine written entirely in Java with a flexible approach and a technical user-base target. It is released under the Apache License. You can create simple or complex workflows, depending on your needs. You can focus your work on the business logic and rules. No more Petri Net or finite state machine coding! You can integrate OSWorkflow into your application with a minimum of fuss. OSWorkflow provides all of the workflow constructs that you might encounter in real-life processes, such as steps, conditions, loops, splits, joins, roles, etc.This book explains in detail all the various aspects of OSWorkflow, without assuming any prior knowledge of Business Process Management. Real-life examples are used to clarify concepts.
Table of Contents (13 chapters)
OSWorkflow
Credits
About the Author
About the Reviewers
Introduction

Other Useful Descriptor Concepts


In this section we will discuss some useful features of OSWorkflow that will simplify your workflow designs.

Finish Actions

An action can be marked as Finish if you want to terminate the workflow after executing it. Remember OSWorkflow will implicitly finish the workflow when arriving at a step that has no actions and therefore no results.

<step id="4" name="Notify employee">
<actions>

<action id="6" name="Notify" finish="TRUE">

<pre-functions>
…
<results>
<unconditional-result old-status="Finished" status=
"Line approval" step="-1" />
</results>
</action>
</actions>
</step>

Auto Actions

An action can be defined as auto when you want the engine to execute it automatically when the process arrives at that step. Only one auto action is executed in a step and its conditions evaluate to true. To make an action automatic just set the auto attribute to true; like the code snippet that follows:

<step...