Multi-Language Catalogs
International companies generally work with various language versions of Aurea CRM, making it important that catalog values are available in all languages.
To work with multi-language catalog values:
- Define the desired languages in the Language info area, see Defining Languages.
- Enable the Catalog Lang. check box for all languages that you wish to use for catalog values.
- Enable the Catalog Base Lang. check box for one of the
languages. The catalog base language forms the unique catalog key together with the
tenant number, and is used as the basis for translating catalog values into other
languages.
If a catalog value has not been defined for a specific language (or the language's parent language), the entry in the catalog base language is displayed when using that language.
Note: Only enable this check box for a single language and do not subsequently change the catalog base language. - Assign the desired languages to stations, see Assigning Languages.Note: If you have defined a language as a catalog language and have not assigned the language to a station, catalog values on that station in the missing language are displayed using the catalog base language.
- Assign all defined languages to the catalog maintenance station.
A column is displayed for each language in the Catalog info area. The first column contains the catalog base language, see Editing Variable Catalogs.
New catalog values should always be added on the catalog maintenance station in the catalog base language, and translations should be entered in the corresponding language columns.
If new catalog values may be added on other stations, check catalog values after communicating and add any missing translations. Catalog changes are communicated to other stations in the next communication cycle, see Communicating Multi-language Catalog values in the Aurea CRM win Administrator Guide.
If you are using different external keys for catalog values in different languages, this is taken into account when importing data, see Importing Catalog Values using External Keys in the Aurea CRM win Administrator Guide.
You can define fixed catalog values in multiple languages in the data model, see Editing Predefined Fixed Catalogs and Adding New Fixed Catalogs.
Use CRM.translation tool to translate variable catalog values and user-defined texts in the data model, see CRM.translation tool.
Behavior of Lock and Validity with Hierarchical Languages
If you have defined sub-languages (language "variants") you can define catalog values for each sub-language, see Defining Language Variants.
The following logic applies for locked catalog values within a language hierarchy:
- catalog value locked in the current language > not displayed in catalog selection dialog
- catalog value locked in the parent language > the first available (i.e. not locked) value from the hierarchy (i.e. the parent's parent etc.) is displayed
- catalog value locked in catalog base language > the value is locked for all languages
- catalog value locked in base language and
mm.ini entry
CatalogLockOnBaseLanguage=off> the value is displayed for all child languages (where it is defined), see [Option] - no catalog values defined in the current (child) language > the first parent language containing values (no matter if locked or not) is used.
The same logic applies for validity periods defined for catalog values.