-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
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
This is the controller panel for Smart Panels app
- is related to
-
-
- Closed
-