This is most easily acomplished in the VDDT Database using MS Access. However, you need to be very cautious so as not to Break your models. Making a Backup copy first is definately a good idea. If you are not comfortable working with Access you might want to get help from someone who is or do the change using the VDDT UI which is safer but more labor intensive.
Making the Change Using MS Access:
1. Create a query to determine what distinct groups are used across all your models in the VDDT databse you are planning to import into Path. You can do this by using the following SQL in a new query:
SELECT ProbabilisticTransitionGroup.Name
FROM ProbabilisticTransitionGroup
GROUP BY ProbabilisticTransitionGroup.Name;
This query will identify all of the distinct transition group names that are currently being used in your database. Looking at this list decide which names are supposed to represtn the same group and for these decide what is a common group name you would like to use.
2. Edit the group names in the ProbabilisticTransitionGroup Table. Open the table and sort ascending by Name. Change the names of the groups that you identified in step 1 to the standardized name. Be careful about not creating any duplicate groups with identical names for the same Project ID. Do not add or remove any records, only edit the Name of existing ones. Do not edit any of the other fields.
3. When importing into Path you will probably still need to uncheck the Use VDDT Definition Codes on Import checkbox because your definitioin codes will probably be out of synch. It is very difficult to standardize these acropss multiple VDDT models and you can definately break your database by messing with the definition codes.
Making the Changes using the VDDT UI:
You can edit Transition Group Names using the File | Properties | Definitions screen (Transition Group Tab). Unfortunately using this method you can only work one VDDT project at a time so it will be labor intensive.