Language support for Content Experiences and Content Publishing
Summarize
Summary of Language support for Content Experiences and Content Publishing
Content Experiences and Content Publishing in ServiceNow support multiple languages, allowing for translations of portal content (excluding calendar), emails, blocks, and to-dos through the translated text table. The platform uses UTF-8 encoding for international characters when a language plugin is activated.
Show less
Key Features
- Language selection at user login enables personalized portal content and to-do translations.
- Emails are sent in the user's specified language from the User [sysuser] table.
- Manual changes to table definitions are required for certain content types to utilize translation support.
- Integration with Localization Framework enhances translation efficiency.
Key Outcomes
Upon configuring language settings, users can access translated content seamlessly. However, when upgrading Content Publishing, automatic translation support is not provided for all fields, and administrators must manually change specific tables to support translations. A backup of data is recommended before making changes to avoid data loss.
Content Experiences and Content Publishing support multiple languages.
Translations are supported for portal content (except calendar at this time), email, block, and to-dos are translatable via the translated text table. For more information, see Translated text table.
Content Experiences and Content Publishing uses UTF-8 for international characters when at least one language plugin has been activated. For more information, see Language internationalization support.
There are several ways to change the language for an instance. For more information, see User specific language.
Once a language has been configured for an instance, when a user logs in, there is a selection for Language. Select the preferred language and portal content and to-do content are translated.
Emails always use the user's language set in the User [sys_user] table. For more information on email notification, see Create email, SMS, or push notification content and User specific language.
- Upgrade and installation
- There are some issues to consider:
- When performing a new May 2022 store installation of Content Publishing for any supported family release (Rome or newer), translations are supported.
- If you have the Washington DC or newer, and upgrading from an older version of Content Publishing to the current version, translations are supported.
- When upgrading your version of Content Publishing, you will not automatically receive translations support for all fields. The following tables are not updated to use translated text instead of the original type field:
- Portal Content (sn_cd_content_portal)
- Block Content (sn_cd_block)
- To-Do Content (sn_cd_content_todo)
- Notification Content (contains emails ) (sn_cd_content_notification)
Warning:Before you change the field types for a table, ensure you perform a back up your data into another column or by exporting the data first. This is a safe guard against losing any data.