How to set up dynamic translation for email notificationsSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Set up dynamic translation to send translated email notifications from your ServiceNow instance. This article provides steps to enable, configure, and test dynamic translation for email notifications. Limitations Email digests cannot be translated. Only emails with localized content are supported.Translation of SMS, push, or messaging content is not supported.CC, BCC, and meeting invitations are not supported. For steps on using static translation, see How to set up static translation on email notifications. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Beginning with the Tokyo release Instructions<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Before you begin Upgrade to Tokyo or a later releaseInstall the following plugins: Glide Notification Translation (com.glide.notification.translation)Localization Framework (com.glide.localization_framework).Include the languages you need for translation (for example, I18N: Spanish Translations, com.snc.i18n.spanish)Dynamic Translation (com.glide.dynamic_translation) Step 1: Enable and configure localization settings 1. Verify that the glide.notifications.translation.dynamic system property is set to True. If the property does not exist, create it. 2. In the filter navigator, go to the Dynamic translation properties (sn_dt_translator_configuration) and make sure your selected translator is active. 3. Before testing a notification, confirm that dynamic translation is active and configured with valid credentials. See the Dynamic Translation overview. The following image shows how a dynamic translation link displays in the activity log: 4. In the filter navigator, go to Localization framework > Settings. The list displays records from the sn_lf_setting table. 5. In the sn_lf_setting table, confirm or create settings for the following three artifacts: email_layout_configurationnotifications_configurationemail_template_configuration 6. In each record, open the Translation preferences tab, select the Enable machine translate check box, and then choose your preferred translator. Step 2: Create or edit a notification for translation 1. Go to System Notification > Email > Notifications [sysevent_email_action] table. 2. Create or open a new notification. 3. Select the Advanced view. 4. Set the Enable dynamic translation toggle switch to True. If you do not see this field, add it using the form layout configuration. See Configuring the form layout. 5. In the sys_user.language field, verify that the recipient's language is correct. Note: If the user's language (sys_user.prefered_language / sys_user_preference [user.language]) matches the default system language property (glide.sys.language), translation does not occur since the source and target languages are the same. By default, the system language property is English. 6. Beginning with the Xanadu release, you can use the preferred language instead of the sys_user.language field. To configure this: Set the glide.email.translation.honour.user_preference property to true. If the the system property does not exist, you can create it.Login as or impersonate the specific userGo to User menu > Preferences > Language & region, and then select the preferred language. The value will be saved in sys_user.prefered_language table with the name user.language Step 3: Test and verify email translation 1. Go to the table used by the notification (for example, Incident, Case, or Task) and make an update that triggers an email from the created sysevent_email notification record. For example, change the Short description field. 2. The system creates a record in the sys_email table containing the message in the default language. 3. A Translated Email Contents tab appears at the bottom of the record showing translated messages for each language. These records are stored in the sys_translated_email_content table. 4. (Optional) To trigger the notification from a flow, set the Send when field (sysevent_email_action.generation_type) to Triggered. Note: Dynamic translation uses translation subflows depending on the translator you select in the dynamic translation configuration. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Translation provider documentation ServiceNow supports the following translation providers by default: IBM Language translatorGetting started with Language Translator Microsoft Language translator overviewGetting started with Language Translator Google Pricing Set up Google Cloud Translator Service spoke. Note: If you are using Google Translate, verify that the Google Cloud Translator Service spoke is installed from the ServiceNow Store. ServiceNow documentation Explore Localization Framework Localization Framework support for email notifications Artifact Configurations. Dynamic translation Configuring the form layout How to set up static translation on email notifications for the first time Multilingual email notifications