Translation - User Interface

The Translation - User Interface page is used to translate or customize the user interface using a language or terminology that is familiar to your users. From the Translation - User Interface page, you can:

  • Extract, customize and import text strings used by the user interface
  • Extract the text strings to Excel
  • Extract text strings from selected domains of the product (for example, Timekeeping, Scheduling)
  • Extract text strings in their context (for example, exceptions)
  • Use find and replace functionality when editing individual property files
Note:

Because the system does validate your input, follow the same naming guidelines and restrictions defined by the required component. In particular, do not use restricted characters.

As a best practice, do not use the following characters in the various Setup components:

| \ \ * ( ) : ; # % ^ ? [ ] = # _ “ & @ < >

Do not use: < > / \ , ; | & #

Do not use: < > / \ ; | #

Do not use:

# The pound/hash character (#) is used to split parameters in Payroll Export Integration for paycode A category of time or money that employees earn, for example, Regular Hours, Bonus, or Sick. and pay rule names. It is also used as a keyword to split integration parameters in Self Service UI for location (Hyperfind A search engine that filters and selects groups of employees through queries that specify conditions or locations (criteria).) filter around IDs and not entity names.

, A comma is used to split a single-comma-separated string for "Licences" (licence name field on Licence entity) Integration parameter in Self Service UI.

Do not use: $ Workflow Designer uses the $ character to define the process variables.

Do not use the following characters in text fields: * % ? : ; = ( ) / [ ] \ | # @ &lt; > "

Do not use: @ # & |

Do not use: / | \ * ( ) : , ; # % ^ ? [ ] =

Grammar treats everything between # as text and is used to specify domain entity names such as paycodes. If any special characters in a domain entity name is used such as "Hours < 4-Week Target" or "Hours > Biweekly Target" exists, then all characters are treated as strings only. This is required because domain entity names have varying reserved characters.

Do not use the following in external leave case code: { } < > [ ] “ ` | \ ^

To translate or customize the UI, complete the following steps.

Complete the following fields:

  • Language — Select the language
  • Country — Select the country
  • Domain — Select the domains (such as Scheduling or Timekeeping) to export. You can select all domains or an individual domain. You can also hold down the Ctrl key to select multiple individual domains. Depending on the domain or domains selected, the corresponding properties are listed in the Group field.
  • Group — Select the applicable property files from the list. Hold down the Ctrl key to select more than one. If you leave the top field blank, all property fields are selected

Click Export. The system downloads an Excel file to the Download folder of your machine.

  1. Click the link to the Excel file. Note that the file name format is language_COUNTRY.xls. For example, if the file is for English and the United Kingdom, the file name is en_GB.xls. You can rename this file, but the name needs to follow these naming convention. Also note that there can only be one export file per locale, although you can also add multiple sheets per locale.
  2. The Excel file contains three columns:
    • Key — Holds the text property name and gives contextual information (for example, used for label, description, tool tip)
    • ORIGINAL_VALUE — Shows how the text property is currently displayed in the UI.
    • TRANSLATED_VALUE — Shows how the text property will be displayed after it has been translated.
  3. In the TRANSLATED_VALUE column, enter the text that will replace the text in the corresponding ORIGINAL_VALUE column. Click Save when finished.
Note:
  • Built in Excel tools such as filtering and sorting allow quick access to required text strings.
  • "Find and replace" functionality allows bulk translation, for example, change Employee to Co-worker.
  1. On the Translation - User Interface page, click Import.
  2. Click Choose File and locate the file to import.
  3. Click Upload. A success message appears when the upload is complete.

Note: Imported files must be 1MB or smaller.

Go to the applicable area of the UI and verify that the changes were made.

When you are satisfied with your modified UI, save the final Excel file. When the product is upgraded, property files will be overwritten and you must re-import this file.

ClosedExample