Migration Points

A migration point is a task in the process template at which a process instance can be migrated to a different version.

Not all tasks are valid migration points. For example:

  • tasks that are on a parallel path, or tasks that may have parallel executions due to multiple tokens flowing on a single path
  • tasks in an embedded sub-process
  • start events or boundary events
  • un-named tasks. (The task name is used to identify a migration point. A well-formed process should therefore not use duplicate task names.)

Valid migration points are automatically identified (and marked internally in the BPEL file) by TIBCO Business Studio at design time.

Note: There are restrictions on the types of change that can be made between the two versions (source and destination) of a migrated process template, as follows:
  • In a normal flow (not a cycle), a task that precedes the migration point in the source version should not be rearranged so that it follows the migration point in the destination version.
  • A task that is concurrent with the migration point in the source version should not be rearranged so that it follows the migration point in the destination version.
  • If compensation is triggered in the destination version for a task that completed in the source version, the compensation defined in the source version will be performed.