Migration UI should make #updateEventTrigger behavior transparent

XMLWordPrintable

    • Type: Feature Request
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: webapp
    • None

      When I create a migration plan with instructions between catching events, I can configure the behavior if the event trigger should be migrated or not (e.g. for message events, if the message should be changed or not, see https://docs.camunda.org/manual/7.7/user-guide/process-engine/process-instance-migration/#events). The default behavior is that the trigger is NOT migrated.

      I can configure this in Cockpit via a checkbox, when I click the migration instruction. The existence of this configuration and its default setting are not obvious to the user. Thus the result of the migration can be unexpected.

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: