[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: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Description |
|
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. |