Use the Manage Languages tool to overwrite UI label values in any language (US English or any language that SAP SuccessFactors currently supports).
The manage language change requests typically arise in two situations:
• You want to change default values of UI text (for example, system text) to better reflect your particular business practices and culture.
• There is an issue with system text (for example, grammar, syntax or key terms). Manage Languages allows for a quicker turnaround while waiting for the system text to be updated in a subsequent patch or release.
Limitations
Value replacement limit: You can overwrite up to 10,000 values per locale using Manage Languages. The default replacement limit is set to 25 values, which you can manually increase up to 10,000 using the Update option at the bottom of the page.
Custom language pack CSV file size limit: The CSV file size limit is 10 MB. If you try uploading a file that is anything more than 10MB, the system will time out and the file will not be uploaded.
Text substitution syntax: You need the text substitution syntax to replace a word throughout the system. Otherwise, each string that includes the string will need to be replaced through Manage Languages.
How can customers change a label in a specific locale that is not available in Text Replacement?
Customers can use the Manage Languages tool from Admin Center to overwrite UI label values in any languages supported by SAP SuccessFactors. The Manage Languages tool is particularly useful in two situations:
Default values of system text can be changed to better reflect a particular business practices and culture.
There is an issue with the current system text (grammar, syntax, key terms, and so on.). Manage Languages allows for a quick turnaround while waiting for the system text to be updated in a subsequent patch or release. Customers should still contact Customer Support so that the issues can be addressed with system level text in future builds.
Changing labels does not update the language phrasing used within the Mobile Application at this time.
Prerequisites
There are two prerequisites that should be enabled in Provisioning → Company Settings:
- Language Packs
- Enable Manage Languages tool
The other prerequisite is the Text Replacement permission in RBP. From the Action Search → Manage Permission Role → Administrator Permissions → Manage System Properties → Text Replacement.
Original Language Pack
In some cases, for example, when the key is hard to read on the screen, it may be helpful to download the full original language pack. In order to do so, follow the two steps below:
1. Download the CSV file of the original language pack. It has all the default system labels.
2. Save the file in a folder where you can find it easily on your computer. You can open your CSV file with Open Office, Notepad or Notepad++. This file, which is the original CSV file, contains the entire list of key values (Key) and their corresponding UI labels. The file should look like the screenshot above.
CSV File of the Manage Languages Tool
As of 1H 2023 release the third column is removed in the CSV file that you get by downloading default labels of a language pack. Users are expected to provide their custom labels in the second column. The third column isn’t in use anymore and accidentally entering data in it can cause failed uploads or other minor issues. The second enhancement is about how to deactivate a custom language pack. Previously, you had to delete a custom language pack to deactivate it; now you only need to deselect the active checkbox beside it, just as you would do to deactivate a built-in language pack.
Automatic Audit for Custom Translation
Custom translation files are automatically audited, and alerts are raised to issues found before updating a custom translation.
The custom translation files are now audited to point out potential issues. The audit result, along with other details, is presented in the dialog that appears by clicking the custom translation link. In the To-Do column of Locale List, there is also a reminder about failed audits and specific keys involved. These keys should be removed from the custom translation file before the upload.
