It should be possible to define multiple migration instructions for the same source activity that apply under different conditions. The condition can be based on variable state.
Use case:
- a coarse-grained task in the source definition is split up into multiple fine-grained task in the target definition, separated by an XOR gateway
- activity instances should be migrated to the correct target activity
AT:
- There is an interface that defines a callback to decide whether a migration instruction applies to an activity instance
- That callback is handed the instruction, the activity instance in question and probably the delegate execution that represents the activity instance
- When defining a migration instruction, an implementation of that interface can be provided (should probably be like a Java delegate, i.e. a String with the Java class name, to enable persisting the migration plan)