-
Type:
Feature Request
-
Resolution: Fixed
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: engine
- even if the migration between these activities may not be supported for activity instances, it is for transition instances, so these instructions should be generated
- it is also not a problem in case you have activity instances of such activities unsupported for activity instance migration but supported for transition instance migration, because this would end in runtime validation failures either way (either because of unmapped leaf activity instances or because of unsupported instructions for activity instances)
Use case:
- a useful migration plan should be generated for processes that consist only of async service tasks