Internationalization

The senior X Platform supports the internationalization of its components in Portuguese (Brazil), English (United States) and Spanish (Spain). The Translation Hub centralizes the translations of all the platform's services, both for Back-end and Front-end. Managed translations are those created by Senior and made available to all customers and also those that customers themselves develop to support a language that was not provided, or so that factory translations have more adherence to the business.

The Translation Hub uses a convention to hierarchize the available texts and has the following levels:

• Global: the key is for general use within the system, that is, it applies to all domains and services. Example: cancel=Cancel.
• Domain: the key is for general use within the domain, that is, it applies to all services. Example: platform.import=Import or hcm.employee=Employee.
• Service: the key is for use within a domain and service, that is, it is valid only for that service. Example: platform.authentication.mfa=Multi Factor.

Example:

Two keys in a Java format file (.properties) can be from all levels in the same file, but there can never be more than two dots (separators) in the key.

platform.backend.menu_group_administration=Administration

platform.backend.menu_group_tenant_management=Tenant Management

Definition of languages

The preferred language can be set by the tenant administrator or by the user themselves, as defined in permissions by the administrator.

The first language selected is the one configured by the user and, if there is no configuration, the one informed in the tenant settings is chosen. If, even so, there is no language configured on the platform, select the browser language. In G7, G5 and SAML authentication, the language is configured on the platform itself, while in LDAP authentication, the user's language is configured and updated in AD.

After changing the language, it is necessary to leave the platform for it to take effect, as the cookies in which the language is informed are generated at the beginning of the session. Some Backend messages take around 15 minutes (OAuth2 token cache) to be translated.

Manage Translations

The import process has two options:

• Import only for the current tenant;
• Import for all tenants (only available for Senior).

All values contained in the file will override those maintained in the Translation Hub for the selected language.

What can you do:

Configure the tenant's preferred language or configure the users' preferred language

To configure the tenant's preferred language as an administrator, go to Technology > Administration > Tenant Management > Configure and select the tenant. In the General section, select the desired language and clickTo save.

To configure the preferred language for each user as tenant administrator, go to Technology > Administration > User Management and select the desired user. In the user data panel, select the language and clickTo save.

Import for current tenant or import for all tenants (Senior)

Oimport procedure for current tenant is required when a translation package is created and made available to a specific tenant. For example, when the tenant himself wants to change the texts displayed by the system.

Alreadyimport procedure for all tenants (Senior) is required when a translation package is created for all tenants. For example, when Senior develops new screens and features, these texts must be available to all Senior customers.

Go to Technology > Administration > Internationalization, clickimport, enter the language you want to change and the file format (properties, json and xlf). Then attach the file and clickimport for a current tenant, or, to import for all tenants, select the all tenants option and click import.

Important

The imported texts take effect immediately, however it may be necessary to reload the system page to obtain the new texts. Additionally, Notepad saves all files in UTF-8 with BOM format, which is not supported by translation-hub nor recommended by the UTF-8 specification. Therefore, the notepad should not be used as a tool for editing translation files. Therefore, import only the changed keys into the file and remove those that continued with the same translation.

Delete translations

Go to Technology > Administration > Internationalization, clickimport, enter the language you want to change and the file format (properties, json and xlf). After that, attach the file with empty keys and clickimport to delete texts translated into a language by importing a file with empty value keys. Example: platform.backend.administration=.

Export translations

Go to Technology > Administration > Internationalization, select a domain or service to be exported and clickExport. After that, enter the language of the translations and the file format (properties, json and xlf) and then clickExport to get the translation package with the translated or untranslated texts of a given language.

How to export the language pack to translate some menu items into English, including custom menus.

Example:

1. Access the senior X Platform;
2. Access Technology > Administration > Internationalization and Expand the Platform > Backend item;
3. click inExport. The screen with options forLanguage It is
   File format.
4. In the fieldLanguage, select the language that will serve as the basis for the translation, for example, Portuguese (Brazil).
5. In the fieldFile format Select the extension that will be used to perform the translation. Currently you can choose between:
   • Ja
   • va (.properties)
   • Flat JavaScript Object Notation (.json)
   JavaScript Object Notation (.json)XLIFF 1.2 (xlf)
6. click inExport. The browser used to access the senior X Platform will download a file in the selected format, with texts in the chosen language.
7. Open the file and change the desired content to the required language and save the file.
8. Again in Technology > Administration > Internationalization. click inimport
   .
9. Select the language that the translated file represents, for example, English (United States).
10. Select the same option used when exporting and upload the file using the designated area on the screen.
11. Configure the scope of this translation, that is, the scope in which the change must be carried out, which may be in theCurrent tenant (logged in) orAll tenants of the environment.
    

Important

The steps above only ensure that the translated language package is loaded on the senior X Platform, while a Tenant's default language configuration must be done in its settings.