Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-5333

I can migrate activity instances between equivalent user tasks where the target process definition contains one additional parent scope

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.5.0, 7.5.0-alpha2
    • Component/s: engine
    • Labels:

      Description

      AT:

      • activity instances are preserved (i.e. activity instance IDs for all migrated activity instances are the same in the migrated process instance)
      • scope executions and the entities they reference are preserved
      • concurrent executions and the entities they reference may not be preserved
      • For newly created scopes, execution listeners and IO mappings are executed
      • Execution listeners can rely that the "upstream" execution and activity instance tree is already migrated (i.e. New scopes are instantiated in a top-down fashion)
      • There is validation that prevents migration of activity instances that are descendants of multi-instance bodies

      Side notes:

      • Execution listeners may not use code that rely on a completely consistent execution tree apart from what is upstream; for example, RuntimeService#getActivityInstance fails when used in an execution listener during migration, because the execution tree is in a mixed state

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              meyer Daniel Meyer
              Reporter:
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: