Magnolia Workflow module is based on OpenWFE.
- Workflow module configuration
DownloadDownload the Workflow module from Magnolia Store or Nexus repository.
InstallingWorkflow is a community module bundled with both the Community and Enterprise Editions. In CE it is available in the
addonsfolder and in EE is typically installed by default. Go to Magnolia Store - Installed modules in AdminCentral to check. To install the module individually, see the general module installation instructions.
UninstallingSee the general module uninstalling instructions and advice.
Workflow module configuration
Since Magnolia 3.6, the workflow module comes configured with an optional dialog allowing authors to enter a comment for publishers during activation. To disable this dialog, go to the Admin Interface and under the Configuration menu entry change the value of
Experimental configuration options
Warning ! The following features are experimental and aren't guaranteed to be safe. Use them at your own risk. Simply do not set any of these configuration options and the workflow module will behave like in previous versions.
Since Magnolia 3.0.2, the workflow module can be configured with the following optional parameters:
- backupWorkitems : if set to true, workitems will be moved to a /backup/ folder in the workspace instead of being deleted. Each assignment or proceeding normally consists of deleting and creating a new workitem. With this option the previous versions are kept and marked as backed up instead. Note that this does not mean they can be reused afterwards, but it makes it possible to at least recover from data or analyze the differences.
- deferredExpressionStorage : if set to true, expressions will not be saved immediately. This improves the performance of complex workflows, because each workflow "step" correspond to one or more expressions, thus many save operations can happen on the expressions workspace. Deferring their storage means that a single save operation is executed every 30 seconds at maximum (if workflows are constantly creating expressions for so long) or after 6 seconds of expressions inactivity. The obvious downside of the performance gain is a loss in safety, since expressions are stored less often.