[DOCU-493] Enabling and disabling the Workflow JBPM module with configuration Created: 22/Nov/13  Updated: 24/Dec/14  Resolved: 24/Dec/14

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: short term
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Gavan Stockdale
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 5.2


Issue Links:
documentation
documents MGNLWORKFLOW-79 Make sure workflow doesn't run (or us... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

MGNLWORKFLOW-79 introduces a new configuration property /modules/workflow-jbpm/config/enabled in the Workflow jBPM module. When the property is set to false, the module does not start.

Document the property in Workflow configuration. Explain that the purpose of this property is to disable the Workflow jBPM module on instances where it is not needed such as public instances, which conserves resources. In the Magnolia bundle for example, the property is true on the author instance and false on the public instance.

Another use case for disabling the module is staging setups that consist of multiple daisy-chained instances. There you only need the workflow module on instances where a workflow process such as review is actually needed. Yet another case for disabling could be a development or test environment where workflow is not part of the test.


Generated at Mon Feb 12 01:09:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.