EmForge Workflow Engine

EmForge uses jBPM from JBoss as workflow engine. It is really great open-source workflow engine and many features were easily implemented in EmForge only because there is used jBPM. We want to say THANK YOU to jBPM development team for so good product!

So, jBPM is quite flexible workflow-engine which allows to user to specify and execute processes. Currently, EmForge uses only about 10% of jBPM features - and we hope, as soon as we will start to use whole 100% power of jBPM it will become a great product!

At the present moment the following jBPM features are used by EmForge:

Process Definition

User may define own processes with using GPD - Graphical Process Designer - Eclipse plugin from JBoss. It is quite useful and simple tool for defining your processes. In Process Definition we are currently processing only Start/End Nodes, Task Nodes and Process Nodes. But there are many other features which can be used in future.

Storing Variables

jBPM allows to store different values as process/task variables. We use this feature to store process-related information.

jBPM Enhancements

EmForge enhances jBPM by the following ways (all these enhancements are done without changing jBPM code - only by using jBPM flexibility):

• Integration with Acegi-Security for getting authentication information
• Storing Process-Owner (user, who started process)
• Storing Process Description (it is used EmForge Wiki Engine to store text-information
• User-Notification about tasks assignment (user notified by email then new task assigned to him)
• many others