The Validation Migrator is shown in the following figure.
Figure 10-16. Validation Migrator
This migrator contains the following two additional import behavior options:
Replace existing special cmds?
If the validation to be migrated references PPM special commands that already exist in the target PPM instance, you can decide whether or not to replace them. This includes both special commands directly referenced by the validation, and also special commands referenced by these special commands. (The default value is No.) Regardless of their values, PPM automatically re-creates special commands that are missing from the destination instance.
Add missing environments?
If the validation to be migrated references environments or environment groups that do not exist in the target PPM instance, you can decide whether or not to create them (assuming that the option has been marked Yes). However, only the environment header information and user data are transferred. Application codes and extension-specific environment tabs are not transferred. The default value is No.
Similarly, environment group application code information is not transferred. If an environment group already exists in the destination instance, it is not updated with environments that were added in the source instance. After migration is complete, if the migrator has created any environments, confirm and complete environment data manually.
For information about the controls in this migrator, see Defining Entity Migrators.
Validation values can also carry context-sensitive user data. When migrating validation values that have such fields, you should manually set up the user data configuration in the destination instance before migration begins.