[MGNLWORKFLOW-191] Workflow launch command doesn't support workflow mapping Created: 16/Jan/14 Updated: 26/Feb/14 Resolved: 31/Jan/14 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | Base |
| Affects Version/s: | 5.0, 5.2.1 |
| Fix Version/s: | 5.3 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Frank Sommer | Assignee: | Espen Jervidalo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| 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)
|
||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||
| Date of First Response: | |||||||||||||
| Visible to: |
Rainer Blumenthal
|
||||||||||||
| Description |
|
In Magnolia 4.x it is possible to configure which workflow definition will be started. The LaunchWorkflowCommand doesn't support this feature. |
| Comments |
| Comment by Espen Jervidalo [ 31/Jan/14 ] |
|
In 4.5 you were able to define workflows to be launched based on subtree-mappings. This is missing in 5 and should be reimplemented. See screenshot for an example. |