Translation - User Interface
Use the Translation - User Interface page ( ) to translate or customize the user interface using a language or terminology that is familiar to your users. From this page, you can:
- Extract, customize, and import text strings in 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.
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.
Setup Applications
As a best practice, do not use the following characters in the various Setup components:
| \ \ * ( ) : ; # % ^ ? [ ] = # _ “ & @ < >
Universal Device Manager (UDM)
Do not use: < > / \ , ; | & #
4500 and In Touch devices
Do not use: < > / \ ; | #
Integration Hub
Do not use:
# The pound/hash character (#) is used to split parameters in Payroll Export Integration for paycode and pay rule names. It is also used as a keyword to split integration parameters in Self Service UI for location (Hyperfind) filter around IDs and not entity names.
, A comma is used to split a single-comma-separated string for "Licenses" (license name field on License entity) Integration parameter in Self Service UI.
Workflow Designer
Do not use: $ Workflow Designer uses the $ character to define the process variables.
People Information
Do not use the following characters in text fields: * % ? _ : ; ( ) | # / \ & ! = < > [ ] , { } .
Event Manager
Do not use: @ # & |
Labor Categories
Do not use: / | \ * ( ) : , ; # % ^ ? [ ] =
KPI Builder
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.
Attendance and Leave
Do not use the following in external leave case code: { } < > [ ] “ ` | \ ^
Do not use the following characters in Attendance Balance Type Names: * % ? _ : ; ( ) | # / \ & ! = < > [ ] , { } .
To translate or customize the UI, complete the following steps.
Step 1: Identify the content to modify
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
Step 2: Export the property files
Click Export. The system downloads an Excel file to the Download folder of your machine.
Step 3: Edit the Excel file
- 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.
-
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.
- In the TRANSLATED_VALUE column, enter the text that will replace the text in the corresponding ORIGINAL_VALUE column. Click Save when finished.
- 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.
Step 4: Import the Excel file
- On the Translation - User Interface page, click Import.
- Click Choose File and locate the file to import.
- Click Upload. A success message appears when the upload is complete.
Step 5: Verify the changes
Go to the applicable area of the UI and verify that the changes were made.
Step 6: Important: Save the Excel file
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.
Example
You want to change the name of "Employee Timecards" to "Associates Timecards."
- On the Translation - User Interface page:
- Select English as the baseline language and specify the United States as the country.
- Select the Timekeeping domain and then select the wtk_web-timekeeping_timecard_strings.properties group.
- Click Export.
- Open the downloaded en_US.xls file and locate the html5.timecard,pages.title key, then enter Associates Timecards in the TRANSLATED_VALUE column and save the file.
- On the Translation - User Interface page, click Import, then click Choose File and locate the en_US.xls file in the download folder. Click Upload.
- Navigate to the Employee Timecards page, and verify that the title is now Associates Timecards.
Customize Report Column Headers
How to custom report-column headers for Healthcare Productivity.
Normally, you cannot edit the column headers of a read-only standard or custom report from Web Designer. However, you can use the properties file to customize any labels including report headers.
Example: You can change the displayed column header for the non-productive mapping categories in the Employee Actual Hours report for Healthcare Productivity. Rename Regular NonProd 1 to Education and Orientation, Regular NonProd 2 to Training, and Regular NonProd 3 to Onboarding.
- Select .
- From the
Translation - User Interface page, export the properties file as follows:
- Select the Language.
- Select the Country.
- In Domain, select Reports.
- In
Group, enter part of the name of the properties file. When it appears in the list, select that file.
Example: For the properties file for the Employee Actual Hours report, enter
employeeactual
so that report_com.kronos.report.design.employeeactual_strings.properties appears in the list. - Click Tap Export.
- Save and open the exported Excel (.xlsx) file.
- Edit the
TRANSLATED_VALUE for the keys that you want to change.
Example: For the
com.kronos.report.design.EmployeeActual.REG_NON_PROD
key, enter Education and Orientation in TRANSLATED_VALUE. Do not edit the ORIGINAL_VALUE. - Save your changes.
- Edit the
TRANSLATED_VALUE for the keys that you want to change.
Example: For the
- From the
Translation - User Interface page, import the edited file as follows:
- Click Tap Import.
- Click Tap Choose File and navigate to and select the file.
- Click Tap Upload.
- Run and verify that the columns are changed in the report as follows:
- Select .
- From the Report Library,
click tap
Run Report
. - In the Select Report panel, select the report.
- Click Tap Select.
- Select the applicable report parameters.
- Select the Output Format.
- Click Tap Run Report.
- Select the report and
click tap
the right arrow
. Click Tap View Report.