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 activation and deactivation (deletion) approval workflows by default. These are provided by the Workflow module. Disabling the workflow may be appropriate for a simple site workforce where there are no separate editor and publisher roles. When the approval workflow is disabled, content will be published to public instances immediately when activation is launched.
Removing the Workflow module disables all workflows, not only the content approval workflow. Don't remove the module if you have custom workflows used for some other purpose.
If you did not install the Magnolia instance yet, choose this option. Disabling workflow involves removing the Workflow module.
To disable workflow before installing Magnolia:
/<CATALINA_HOME>/webapps/<contextPath>/WEB-INF/libdirectory on all Magnolia instances:
If you already installed Magnolia and want to disable workflow afterwards, choose this option.
Each app that allows you to activate content has an
activate action that typically triggers an
activate command. Here is an example command from the Pages app:
activate command in the app delegates the work to an
activate command in the
workflow catalog. The second command then triggers the approval workflow. The
commandName property value follows the pattern:
commandName property so that it triggers a command that does not involve workflow. The Activation module provides two such commands:
default-activatejust activates the content. No workflow, no versioning.
versioned-activateactivates and versions the content. No workflow.
Here is an example:
Change the command for all apps where you don't want a workflow. Each app has its own activate command. However, only the Pages app triggers an approval workflow by default.
Deactivation works the same way. In the Pages app, the
deactivate action triggers a command that delegates the work to the
workflow-deactivate command. Change it to a non-workflow alternative.
default-activate command doesn´t work with personalization and variants, personalization has its own command