Workflow module

Collaboration Bundled: DX Core

Download	Multiple submodules
Edition	DX Core
License	MLA
Issues	MGNLWORKFLOW
Maven site	Workflow
Latest	6.0.12

Download

Multiple submodules

Edition

DX Core

License

MLA

Issues

MGNLWORKFLOW

Maven site

Workflow

Latest

6.0.12

Magnolia comes with a four-eye content approval workflow. You can reconfigure the default workflow to include more approval steps, more participants and decision points. Workflow is configured in the Workflow and Workflow jBPM modules. The workflow engine is based on the JBPM Business Process Management (BPM) Suite.

Modules

Magnolia’s workflow implementation consists of four modules.

Four modules

Module	Description
Workflow	An engine-agnostic integration module. Enables the necessary integration points for Magnolia to communicate with a workflow engine.
Workflow jBPM	Magnolia’s jBPM integration module. Takes care of loading BPMN process definitions and workitem handlers. Implements the concepts of RuntimeManager and RuntimeEnvironment from jBPM 7.
Drools JCR persistence	Used for persisting work items and sessions to JCR.
jBPM JCR persistence	Used for persisting processes to JCR.

Module

Description

Workflow

An engine-agnostic integration module. Enables the necessary integration points for Magnolia to communicate with a workflow engine.

Workflow jBPM

Magnolia’s jBPM integration module. Takes care of loading BPMN process definitions and workitem handlers. Implements the concepts of RuntimeManager and RuntimeEnvironment from jBPM 7.

Drools JCR persistence

Used for persisting work items and sessions to JCR.

jBPM JCR persistence

Used for persisting processes to JCR.

The Kie modules are heavily inspired by jBPMs own JPA implementation.

Installing with Maven

Bundled modules are automatically installed for you.

If the module is unbundled, add the following to your bundle including your project’s <dependencyManagement> section and your webapp’s <dependencies> section. If the module is unbundled but the version is managed by the parent POM, add the following to your webapp’s <dependencies> section.

<dependency>
  <groupId>info.magnolia.workflow</groupId>
  <artifactId>magnolia-module-workflow</artifactId>
  <version>6.0.12</version> (1)
</dependency>

1	Should you need to specify the module version, do it using `<version>`.

<dependency>
  <groupId>info.magnolia.workflow</groupId>
  <artifactId>magnolia-module-workflow-jbpm</artifactId>
  <version>6.0.12</version> (1)
</dependency>

1	Should you need to specify the module version, do it using `<version>`.

<dependency>
  <groupId>info.magnolia.workflow</groupId>
  <artifactId>drools-jcr-persistence</artifactId>
  <version>6.0.12</version> (1)
</dependency>

1	Should you need to specify the module version, do it using `<version>`.

<dependency>
  <groupId>info.magnolia.workflow</groupId>
  <artifactId>jbpm-jcr-persistence</artifactId>
  <version>6.0.12</version> (1)
</dependency>

1	Should you need to specify the module version, do it using `<version>`.

Be mindful of the version discrepancy between the Workflow modules and the core module.

Compatibility module

If you have custom code relying on classes from the Magnolia 5 UI Workflow module, you must do one of two things:

Update your code for the Magnolia 6 UI Workflow module.
Use the magnolia-workflow-compatibility module together with the magnolia-core-compatibility and magnolia-diff-compatibility modules.

Usage

See Workflow.

Feedback