As a user, I can launch the activation workflow so that I can do the review process
(MGNLWORKFLOW-43)
|
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | Base, jBPM |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Jozef Chocholacek | Assignee: | Jozef Chocholacek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: | |
| Sprint: | Alpha 3, Iteration 2013-12, Iteration 2013-13, Iteration 2013-14, Iteration 2013-15, Iteration 2013-16 |
| Description |
|
The current way of passing parameters (variables) to/from the workflow (running process) seems to be a bit overcomplicated. Invent something more straightforward. |
| Comments |
| Comment by Jozef Chocholacek [ 18/Apr/13 ] |
|
The original idea of abandoning the mgnlData process variable is not feasible, as it is not possible to browse the process variables - you have to know the name to obtain one. The ProcessContext interface does not have getVariables() method, just getVariable(String name) and setVariable(String name, Object value) methods. |