![]() |
|
|
|
|
Issue Type:
|
![Task]() Task
|
|
Affects Versions:
|
short term |
|
Assignee:
|
Gavan Stockdale
|
|
Components:
|
content |
|
Created:
|
22/Nov/13 4:19 PM
|
|
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.
|
|
Environment:
|
Magnolia 5.2
|
|
Project:
|
Documentation
|
|
Priority:
|
![Neutral]() Neutral
|
|
Reporter:
|
Antti Hietala
|
|
Security Level:
|
Public |
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
