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: ; } } Beginning with the Tokyo release, you can send dynamically translated email notifications from your instance. The following instructions provide general guidance and steps to implement dynamic translation. Things to consider about dynamic translation: You cannot translate email digests. You can only send emails with localized content. Translation of SMS, Push, or messaging content is not supportedCC, BCC, and meeting invitations are not supported For steps on using static translation in your emails, see this related knowledge article. 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 newer 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, com.snc.i18n.spanish / I18N: Spanish Translations)Dynamic Translation (com.glide.dynamic_translation) Step 1: Enable and configure localization settings 1. Verify 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 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 do 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. 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. 2. The system creates a record in the sys_email table containing the message in the default language. 3. A new tab, Translated Email Contents, appears at the bottom of the record showing translated messages for each language. These records come from the sys_translated_email_content table. 4. (Optional) To trigger the notification from a flow, set the sysevent_email_action.generation_type field Send when 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: ; } } By default, ServiceNow supports the following translation providers: IBM Language translatorGetting started with Language Translator Microsoft Language translator overviewHow to sign upGetting started with Language Translator Google Pricing Set up Google Cloud Translator Service spoke. Important: If you are using Google Translate, verify that the Google Cloud Translator Service spoke is installed from the ServiceNow Store. Explore Localization Framework Localization Framework support for email notifications To use the Localization Framework to fulfill the translation requests, see Artifact Configurations. Dynamic translation How to set up static translation on email notifications for the first time Multilingual email notifications