-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
User Story (Required on creation):
As a developer when executing a migration the event trigger for message catch events should be updated by default. The name of the message catch event is changed if a subsystem is refactored (e.g. message renaming from "EvaluationOrderClose" to "EvaluationOrderCompleted"). This ensures that all migrated processes can process the messages with the adopted name and avoid unnecessary errors, as there is no case in which the trigger should not be updated.
Functional Requirements (Required before implementation):
- In the Cockpit UI for process instance migration, the "update event trigger" flag (https://docs.camunda.org/manual/7.17/webapps/cockpit/bpmn/process-instance-migration/#set-update-event-trigger-flag) is set for all migration instructions between message events
- Review other event types and decide if the default value should be changed too (e.g. for timer events, not checking the flag by default may be better because otherwise the timer gets reset)
Limitations of Scope (Optional):
- The default behavior in the REST and Java API does not change (to preserve backwards compatibility and avoid complexity)
Hints (Optional):
This is the controller panel for Smart Panels app
[CAM-14502] Update event trigger for message catch events by default
| Link | New: This issue is related to SUPPORT-12938 [ SUPPORT-12938 ] |
| Sprint | New: SOON [ 95 ] |
| Sprint | Original: SOON [ 95 ] | New: Potential for 7.18 [ 94 ] |
| Rank | New: Ranked higher |
| Rank | New: Ranked higher |
| Sprint | Original: Potential for 7.19 [ 94 ] | New: Release 7.19 [ 123 ] |
| Rank | New: Ranked lower |
| Description |
Original:
*User Story (Required on creation):*
As a developer when executing a migration the event trigger for message catch events should be updated by default. The name of the message catch event is changed if a subsystem is refactored (e.g. message renaming from "EvaluationOrderClose" to "EvaluationOrderCompleted"). This ensures that all migrated processes can process the messages with the adopted name and avoid unnecessary errors, as there is no case in which the trigger should not be updated. *Functional Requirements (Required before implementation):* *Limitations of Scope (Optional):* *Hints (Optional):* |
New:
*User Story (Required on creation):*
As a developer when executing a migration the event trigger for message catch events should be updated by default. The name of the message catch event is changed if a subsystem is refactored (e.g. message renaming from "EvaluationOrderClose" to "EvaluationOrderCompleted"). This ensures that all migrated processes can process the messages with the adopted name and avoid unnecessary errors, as there is no case in which the trigger should not be updated. *Functional Requirements (Required before implementation):* * In the Cockpit UI for process instance migration, the "update event trigger" flag (https://docs.camunda.org/manual/7.17/webapps/cockpit/bpmn/process-instance-migration/#set-update-event-trigger-flag) is set for all migration instructions between message events * Review other event types and decide if the default value should be changed too (e.g. for timer events, not checking the flag by default may be better because otherwise the timer gets reset) *Limitations of Scope (Optional):* * The default behavior in the REST and Java API does not change (to preserve backwards compatibility and avoid complexity) *Hints (Optional):* |