[MGNLWORKFLOW-16] Enable/Disable Workflows Created: 27/Nov/12  Updated: 17/Mar/14  Resolved: 17/Mar/14

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

Type: Improvement Priority: Neutral
Reporter: Marvin Kerkhoff Assignee: Espen Jervidalo
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MGNLWORKFLOW-211 Simplify configuration of workflow 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   

In my opinion it is very comfortable if it is possible to enable all workflows with a single enable nodeData in the module root. It is often possible to have Versioning support but no Workflow for this. In this case you must delete the workflow config in every Module (DMS,Data,Website) to get a versioning without workflow support.



 Comments   
Comment by Jozef Chocholacek [ 27/Nov/12 ]

I think it would be also nice to have a possibility to turn the workflow on/off as a whole, by setting a system and/or config-node property. Could be useful in case of a bug-hunting.

Comment by Espen Jervidalo [ 07/Oct/13 ]

This is solved by choosing the right command catalog. If you take a look at the pages app configuration. You have a website catalog, which delegates to workflow-catalog. If you want your content app to fall back to only versioning, you choose the "versioned" catalog from activation module and you're done. This is one single point which steers your publication, so ui actions and e.g. a web service would use the same pattern.

Comment by Espen Jervidalo [ 17/Mar/14 ]

Enable and disabling workflow is a matter of choosing the right command catalog and making sure your actions are configured correctly. This has been simplified a lot since 5.3 and is documented in http://documentation.magnolia-cms.com/display/DOCS/Enable+Workflow+in+Content+Apps

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