[magnolia-dev] [JIRA] (MGNLWORKFLOW-257) Deactivation command misses commandName property
Roman Kovařík created MGNLWORKFLOW-257 Deactivation command misses commandName property Issue Type: Improvement Assignee: Espen Jervidalo Components: jBPM Created: 11/Jun/14 3:09 PM 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. Fix Versions: 5.4 Project: Magnolia Workflow Module Priority: Neutral Reporter: Roman Kovařík This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-257) Deactivation command misses commandName property
Roman Kovařík
updated MGNLWORKFLOW-257
Deactivation command misses commandName property
Change By:
Roman Kovařík
(11/Jun/14 3:13 PM)
Description:
To be able to easily override activation with custom activation
Dectivation currently doesn't work because {{deactivation}} command uses default {{commandName=activate}} property.# Add {{/modules/workflow/
commands
one has to design a custom jbpm process atm
/workflow/activate/deactivate@commandName=deactivate}} property
.
It would simpler if one could simply change the
# Add also {{/modules/workflow/commands/workflow/activate/activate@
commandName
in the
=activate}} property to make
configuration
clear
.
# Add update tasks for 1.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-257) Deactivation command misses commandName property
Roman Kovařík
updated MGNLWORKFLOW-257
Deactivation command misses commandName property
Change By:
Roman Kovařík
(11/Jun/14 3:14 PM)
Description:
Dectivation currently doesn't work because {{deactivation}} command uses default {{commandName=activate}} property.# Add {{/modules/workflow/commands/workflow/activate/deactivate@commandName=deactivate}} property.# Add also {{/modules/workflow/commands/workflow/activate/activate@commandName=activate}} property to make configuration clear.# Add update tasks
for 1
.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-257) Deactivation command misses commandName property
Espen Jervidalo
updated MGNLWORKFLOW-257
Deactivation command misses commandName property
Change By:
Espen Jervidalo
(11/Jun/14 3:15 PM)
Description:
Dectivation currently doesn't work because {{deactivation}} command uses default {{commandName=activate}} property.# Add {{/modules/workflow/commands/workflow/activate/deactivate@commandName=deactivate}} property.# Add also {{/modules/workflow/commands/workflow/activate/activate@commandName=activate}} property to make configuration clear.# Add update tasks
for 1 & 2
.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
