Magnolia 5.6 reached end of life on June 25, 2020. This branch is no longer supported, see End-of-life policy.
Magnolia ships with a "four-eye" content approval workflow. Workflow is configured in the Workflow and Workflow jBPM modules. The workflow engine is based on the JBPM Business Process Management (BPM) Suite.
Magnolia's workflow implementation consists of four modules.
|
The Kie modules are heavily inspired by jBPMs own JPA implementation.
Maven is the easiest way to install the modules. Add the following dependencies to your bundle:
Be mindful of the version discrepancy between the workflow modules and the core module.
<dependency> <groupId>info.magnolia.workflow</groupId> <artifactId>magnolia-module-workflow</artifactId> <version>5.8</version> </dependency>
<dependency> <groupId>info.magnolia.workflow</groupId> <artifactId>magnolia-module-workflow-jbpm</artifactId> <version>5.8</version> </dependency>
<dependency> <groupId>info.magnolia.workflow</groupId> <artifactId>drools-jcr-persistence</artifactId> <version>5.8</version> </dependency>
<dependency> <groupId>info.magnolia.workflow</groupId> <artifactId>jbpm-jcr-persistence</artifactId> <version>5.8</version> </dependency>
With Magnolia 5.6 we've begun removing the old Content API from our modules. If you have custom code relying on classes from the old workflow module then you must do one of two things:
magnolia-workflow-compatibility
module together with the magnolia-core-compatibility
and the magnolia-diff-compatibility
modules.See Workflow.