Setting a System Language - Globalization

In Archer, globalization involves languages, locales, and translation. Archer globalization features enable administrators and users to set their preferred language, locale, and timezone to meet their language and cultural needs.

Languages

Multiple language translations of Archer navigation, solution content, and documentation are available for licensing. A language must be licensed and activated in an instance to make its Archer navigation translations available. At least one language license is included with the original product license, and is set as the default language during installation. You can add language licenses to provide more translations to users.

Archer navigation is displayed to users in the language associated with their locale. If the language associated with their locale is not active, the default language is displayed instead. Administrators associate locales with a language to display formats used for dates and currency, and localized Archer functions such as calculations, time-based filtering, and reporting.

Archer supports the following languages:

  • Chinese (Simplified)
  • English
  • French
  • German
  • Italian
  • Japanese
  • Portuguese (Brazilian)
  • Spanish

Locales

Locales are defined by language and country to enable users to see Archer content in the format applicable to their culture. A locale can only be associated with one language, and multiple locales can be associated with the same language. A locale cannot be removed from a language if the locale has associated users.

Administrators can set a default locale for users and user groups; however, the locale assignment is associated only with individual users and not with groups. The assignment of a user group to a locale assigns the locale to the current set of users in the group. Future user additions to the group do not get the locale assignment, and future user removals from the group do not remove the user locale setting. Users with update permissions for their accounts can set their locale to a non-default locale.

A complete list of supported locales is available on the Manage Locales page.

Translations

A translation refers to a natural-language translation of objects that you have created in Archer. The language used to create an object is its design language. The default instance language is specified during installation. All descending Archer objects, such as Module Level and Fields, inherit the default language from the root object.

Important: When exporting a language, the content a user enters is excluded from the translation, even when the objects are translated.

The following table shows the root objects and the descending level 1 and 2 objects that inherit the default language:

Root Objects

Level 1 Objects

Level 2 Objects

Applications
Questionnaires
Sub-forms
Global Values Lists
Solutions
Workspaces
Dashboards
iViews
Letterhead Templates
Folders

Module Level
Reports
Questionnaire Values Lists

Fields
Layout
Event Rules
Event Actions
Questionnaire Campaigns
Questionnaire Rules
Field Filter Properties
Notifications

You can move translations for packaged items from one instance to another, which enables testing a translation before users have access. When importing Archer core solutions, you must install a valid license on the importing instance before installing the translation.