Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
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.
<version/>in the dependency.
Be mindful of the version discrepancy between the workflow modules and the core module.
We have been gradually removing the old Content API from our modules since Magnolia 5.6. If you have custom code relying on classes from the old workflow module then you must do one of two things:
- Update your code for the new version of the workflow module.
- Or you can use the
magnolia-workflow-compatibilitymodule together with the
Add the following snippet to you pom file: