Open Source BPM using GemStone/S, Orbeon and others
BPM packages for GemStone/S ® implement the BPM standart. The application code can be found at (https://github.com/brunobuzzi/BpmFlow). Each BPM model is created in Bizagi Modeler ® and then exported as XPDL file.
The XPDL file is imported in the BPM Meta Model Execution Engine and it can be instantiated and executed inside GemStone/S.
The BPM application can interact with other systems like Orbeon ® or use Seaside components.
Inside Bizagi Modeler if a task has the extended attribute -seasideComponent- then is a Seaside task if not then is an Orbeon form.
The execution engine will show a Seaside component or an Orbeon form depending on the task's definition in the Bizagi Modeler.
Orbeon is an optional application that interact with the BPM application (can be used or not).
GemStone/S Packages
Orbeon:
- Store Orbeon Form Definitions and Instances
- It creates from the XML string an object representation of the Form Definition or Instance .
Query Orbeon Form Definitions and Instances.
- Different queries can be applied to Form Definitions and Instances.
Process Orbeon Forms in XML format after being POST by the user.
- Orbeon do a POST to a REST services and it is processed and added to GemStone/S object base.
- Synchronization between Orbeon MySQL Database and GemStone/S Object Database.
BPM Implementation:
- Import XPDL files from Bizagi Modeler.
- Others modeler tools can be added using XPDL import.
- Each Bizagi element is mapped to an ElmentDefinition class.
- The Bizagi process creates a BpmProcessDefinition instance representing the process definition inside GemStone/S.
- The BPM Execution Engine instantiate and execute instances of BpmProcessDefinition giving life to the process.
- Each Bizagi task is either an Orbeon Form or a Seaside Component.
- Support for Gateways:
- Creation Conditions: [:form | form amount > 15000]
- Display Orbeon in a IFrame or in a different page (configurable by user).
- Backoffice and Frontoffice web applications.