Matching Translation

Here are some principles in how translations are matched to consider when setting up translations:
  • Items entered into fields in the translations classes should always be thought of as constraints to the matching process. The fewer constraints defined, the more likely it is to have a translation match.
  • Generally, only one property translation or generalized translation matches and, therefore, only one translation is returned for a given property name.
  • Multiple translations occur only if there are multiple applicable translations that have the same value in the Associated Class, Interface Category, and Translation ID fields. For example, if you want to see the source property Part Number result in two properties in another tool, such as PARTNO and PART# that have the same value.
  • For property name translation, if the Associated Class is different between two translations and both associated classes are ancestors of the Explore class defined, the translation with the associated class nearest the leaf in the class hierarchy is selected.
  • Explore related property name translations and class name translations are checked before generalized translations. One reason for this checking order is that it enables the integration program to distinguish between class and property names in case the exact same string is used to define both a class and a property.