[MGNLWORKFLOW-239] CommandName should be configurable in config rather than in jbpm process definition Created: 22/May/14 Updated: 11/Jun/14 Resolved: 05/Jun/14 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | jBPM |
| Affects Version/s: | None |
| Fix Version/s: | 5.4 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Philip Mundt | Assignee: | Espen Jervidalo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| 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)
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Description |
|
To be able to easily override activation with custom activation commands one has to design a custom jbpm process atm. It would simpler if one could simply change the commandName in the configuration. |
| Comments |
| Comment by Espen Jervidalo [ 06/Jun/14 ] |
|
Note: the property is called "commandName" and not "activateCommand" |