Translating custom content
Summarize
Summary of Translating custom content
The ServiceNow AI Platform allows for the translation of custom content, either to supported languages or to unsupported languages through a recommended Localization Framework application. It is crucial to provide your own translations for custom applications and modifications, as the platform does not offer automatic translation capabilities.
Show less
Key Features
- Translation Methods: Different approaches are required based on the type of content being translated, such as field labels, UI pages, Service Catalog items, and Service Portal widgets.
- Translation Records: For each English message, create corresponding Message records for other languages, using the gs.getMessage calls for UI pages and externalizing text in Service Portal widgets.
- Unsupported Languages: To translate into unsupported languages, create Choice records and follow the export/import process for additional translation records.
- Custom Notifications and Surveys: Create separate versions for each language and implement business rules to manage user access to the correct language version.
Key Outcomes
By effectively utilizing these translation methods, you can ensure that your custom content is accessible in various languages, enhancing user experience and broadening your application's reach. Regularly repeat the translation process whenever content is edited or updated to maintain consistency across languages.
Translate content you create or modify to a supported language or add an unsupported language.
ServiceNow provides translations of the base system UI strings in supported languages through the internationalization (I18N) language plugins. For applications you create and modifications you make to the ServiceNow AI Platform® content, you must provide your own translations. You can also provide any translations to unsupported languages that ServiceNow does not provide translations for. The ServiceNow AI Platform does not provide any automatic translation capability.
| What needs translation | Approach to take | Resources |
|---|---|---|
| Field labels in a table for a customer-created application |
|
|
| HTML in a UI page in a customer-created application |
|
Translate a client script message |
| Service Catalog items |
|
|
| Service Portal widget |
|
|
| Edit a translation provided in a plugin |
|
Export and edit translation records |
| Translate an instance to an unsupported language |
|
Translating to an unsupported language |
| Support Chat texts | Support Chat is mostly translated through the I18N language plugins. If you customize any Support Chat texts, follow the procedure for Service Portal widgets. | Internationalize a widget in Service Portal documentation |
| Notifications and surveys | System Localization does not cover platform notifications or surveys. The usual approach is to create a separate version of each survey or notification in each language and use business rules to send the right language version to the right end user. | — |