[MGNLWORKFLOW-79] Make sure workflow doesn't run (or use resources) unnecessarily on public instances Created: 04/Jul/13  Updated: 22/Nov/13  Resolved: 09/Jul/13

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0

Type: Story Priority: Critical
Reporter: Jozef Chocholacek Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLEE-274 Make sure workflow doesn't run (or us... Closed
causality
caused by MGNLEE-271 Create basic M5 EE bundle (CE + licen... Closed
documentation
to be documented by DOCU-493 Enabling and disabling the Workflow J... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Title was - "Update magnolia_control.sh (.bat) to remove workflow modules from Public instance on install"
Description was - The installer copies the whole Author instance, but so far we don't want to run workflow modules on public instance. So the magnolia-module-workflow-*.jar and META-INF/context.xml files should be removed from the public instance (or at least renamed, to prevent their use).



 Comments   
Comment by Magnolia International [ 09/Jul/13 ]

The workflow jBPM module now has an enabled flag. If the flag is set to false, the module won't start. The module's version handler sets this flag to true or false depending on the instance being an author or public. This gives users the possibility to use the workflow module on public instances (or staging, or anything else)

Generated at Mon Feb 12 10:06:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.