Activation and Workflow
When you activate a page you might be surprised with a message, that the page has been added to the inbox.
Activation and Workflows
This message says that the activation has triggered a workflow process.
It's quite common that after editing a page you want someone else to double-check and make sure there are no errors. For these scenarios Magnolia has introduced the OpenWFE workflow.
As a workflow sample we have created an //activation workflow// , which demonstrates the possibilities you have. The workflow process definition is configured under "Configuration/Workflow" and the triggering is done through a // command chain // , configured under "modules/adminInterface/commands".
The openWFE workflow Magnolia is using is very powerful. In the mentioned activation workflow sample it's also possible to trigger E-Mails whenever a page gets activated.
Disable Workflow You can disable the activation workflow. To do so, take first a look at the command chain configuration in "modules/adminInterface/commands".
The command chain is organized as follows: 1) The name of the //repository// this command chain is assigned to. 2) A name for the //command chain// , which is defined with sub content nodes. 3) The command chain has 3 commands: " //version// ", " //startFlow// " and " //alert// ". 4) The command to start the workflow.
The way this command chain works:
- First a version of the page is added to the versions.
- Then the workflow "activation" (defined in property workflowName) is started.
- And at last an Alert message is triggered.
To remove the start workflow command simply delete the " //startFlow// " content node. Same would have to been done fot the alert message.
The // command chain // functionality is open and flexible. You can create your own commands, example to trigger an E-Mail on certain activities.
Activation and Versioning
Magnolia would allow to create a version for every piece of content you change. However, this would blow up physical memory significantly.
Therefore we use the activation command chain for versioning. This means that on every page activation a version is created and added to the version file.
You could remove versioning by simply removing the //version// command from the command chain, but that is not recommended. Instead, reduce the amount of versions for a page. This is a configurable property in "Configuration/server/version".
Property active true = Enable versioning false = Disable versioning
Property maxVersionIndex Define the maximum amount of versions allowed per page. When the maximum amount is reached, the oldest versions will be deleted.
