[MGNLWORKFLOW-257] Deactivation command misses commandName property Created: 11/Jun/14  Updated: 12/Jun/14  Resolved: 11/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: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLWORKFLOW-239 CommandName should be configurable in... Closed
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   

Dectivation currently doesn't work because deactivation command uses default commandName=activate property.

  1. Add /modules/workflow/commands/workflow/activate/deactivate@commandName=deactivate property.
  2. Add also /modules/workflow/commands/workflow/activate/activate@commandName=activate property to make configuration clear.
  3. Add update tasks for 1 & 2.

Generated at Mon Feb 12 10:08:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.