[MGNLWORKFLOW-94] Prefer jcr defined workflow definitions over the one in the files Created: 23/Jul/13 Updated: 30/Jul/13 Resolved: 23/Jul/13 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | jBPM |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Description |
|
Currently, upon installation, the jbpm definitions will not go into jcr but stay in the file system. When loading workflows values from jcr are considered but will always be replaced by the ones from the filesystem. Both should be changed - much like it's implemented in 4.5. Like that users:
|