Defining the migration policy

When you migrate from one snapshot to another, you can define how to handle orphaned tokens.

1. From the action menu of the snapshot that you want to migrate, click Generate Migration Policy. This action sets the target of the migration.
2. In the Generate Migration Policy File window, click the snapshot that you want to migrate from. Click OK. This action sets the source of the migration. The snapshot that you installed now has a migration policy in the Migration Policy Available section. For example, if you are migrating Snapshot 2.0 to Snapshot 3.0, the migration policy file is in Snapshot 3.0 but is named Snapshot 2.0.
3. Expand the migration policy section and click Edit for the policy with the same name as the source snapshot.
4. From the lower section of the editor, select the BPD or a subprocess. The upper section displays the diagram for the BPD or subprocess that you select in the lower section. The steps in the diagram that could potentially have an orphaned token are listed in the lower section. The first of these steps are highlighted in the upper and lower parts.
5. For each step, set whether orphaned tokens that occur at that step should be removed or deleted.
6. If you choose to move an orphaned token, the upper part of the editor splits into left and right sections. Use the diagram in the right section to select the step to move the orphaned token to. For example, you have a subprocess that could generate an orphaned token. You select to move these orphaned tokens. In the right diagram, you browse until you see the step that you want the token to move to and select it. When you select the target step for the move, the lower part updates to add the name of the target.
7. When you have defined how to handle orphaned tokens for the entire file, click Save.