Cannot cancel transition instances when execution tree is expanded/compacted in same transaction

XMLWordPrintable

      When a transition instance is cancelled in a scope and the execution tree structure within that scope changes in the same transaction before the cancellation is executed, then the transition instance cannot be cancelled.

      Examples:

      • sub process with a single active transition instance; reproduce steps: in one modification, start another activity and cancel the transition instance; cancelling the transition instance fails
      • sub process with two two active transition instances; reproduce steps: cancel both transition instances; cancelling the second fails

      The reason is compaction of the execution tree when there is only one active path of execution in a scope and expansion when there is more than one. Since we use the execution id as the transition instance id, the transition instance id after expansion/compaction may not be valid anymore since another execution may be responsible for executing the async continuation then.

        This is the controller panel for Smart Panels app

              Assignee:
              Michael Schoettes
              Reporter:
              Thorben Lindhauer
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: