[MAGNOLIA-1134] Default workflow : versioning should happen in the activation workflow rather than in the activation command-chain Created: 12/Oct/06 Updated: 10/Jan/14 Resolved: 10/Jan/14 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | workflow |
| Affects Version/s: | 3.0 RC3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Daniel Lipp |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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 |
|
The idea being that, in case of rejection, the editor could do corrections on the current unversioned page, while activation (upon "proceed" by the publisher ) would occur on a fixed version. |
| Comments |
| Comment by Magnolia International [ 12/Oct/06 ] |
|
This is a further improvement from |
| Comment by Jan Haderka [ 13/Mar/12 ] |
|
How would moving versioning inside of the workflow ensure that activation occurs on fixed version? Activation is already using version created in previous step in case versioning command is enabled. Keeping it outside of workflow allows simple switching on and off of the activation and ensures creation of the version at the very same moment when editor clicks the activate button/menu. If the only purpose of this issue was to ensure that activation is using versioned content, then the issue should be closed as obsolete. |