Since local and global type names are created and updated in two independent tools there can be name conflicts when a global type is linked to a project or a project is synchronized with the global types.
The main rule is that global type names are leading and you as a modeler can only adjust the names of the local custom types.
The following situations may happen:
1. The name of the global type that is going to be linked to a project is the same as an already existing local type name. Then the system will try to merge them automatically.
2. You rename a local type and try to give it the name of an already linked global type. In general, you cannot give a type a name of an existing type but this is an exception. Such an attempt to rename will be treated as a request to merge two types.
3. The Tables manager has renamed the global type and the new name is the same as the name of a local type in your project. This name conflict will be found during synchronization. Since the global type cannot be renamed in the Engage Process Modeler there are two solutions possible: either the local type will be automatically merged with the global one (in the same way as in the p. 1 and p. 2) or the local type will be renamed. Since the merging operation is irreversible and we do not know in advance if the project developer really wants to merge the types the second solution is implemented. If this situation happens you will get the following message:
Now, you know that your former local type Locations is now called Locations1 because Locations is a new name of a global type. If you think that these two types are the same you can still rename Locations1 into Locations merging these types yourself.