Managing Localization

The Conga Platform provides administrators with provisions for configuring locale settings and translating text, strings, and labels to any language suitable for the specific region-wise audience. You can either use the Translation Workbench user interface or REST APIs as per your business needs.

Every tenant (customer) is associated with a specific default locale, referred to as the organization-wide or tenant locale. When you want to localize your tenant to accommodate one or more locales other than the tenant locale, use the Translation Workbench administrator tool. 
To open Translation Workbench, navigate to the App Launcher () icon from the top left corner > Admin Console > Translation Workbench. By default, a list of modules is displayed.

Using the Translation Workbench, you can export strings that reside in your tenant database to a separate file, provide the exported strings to a translator, and then import the translated strings back to the tenant database. Each translated string is stored in the tenant database as a key-value pair, with the key representing the translation and the value representing the translation of the string for the given locale. In this way, there is a single key that identifies all translations of a specific string. Translation keys are also tied to a module, which indicates where the string(s) are used in the application.

In the absence of user-level locale preference, the system considers organization-level preference and applies translation accordingly. For example, if the organization level locale is 'English' and the logged-in user's locale is 'Chinese', the application will be translated into 'Chinese' for this specific user.