How to set up static translation for email notifications - Support and Troubleshooting

How to set up static translation for email notifications Summary .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: ; } } Starting with the Tokyo release, you can configure static translations for email notifications. This lets you send localized email content to users in their preferred languages. The following instructions provide general guidance and steps to implement static translation in your instance.

Things to consider about static translation:

You cannot translate email digests Translation of SMS, Push, or messaging content is not supported CC, BCC, and meeting invitations are are not supported For steps on using dynamic translation in your emails, see this related knowledge article.

Release .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-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 release Install 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) Step 1: Enable and configure localization settings 1. Verify the glide.email.outbound.static_translation.enabled system property is set to True . If the property does not exist, create it.

2. In the filter navigator, go to Localization Framework > Settings (table name sn_lf_setting)

3. In the sn_lf_setting table, confirm or create settings for the following three artifacts:

email_layout_configuration notifications_configuration email_template_configuration 4. In the workflow Preferences tab, select the Localization fulfiller group. Members of this group can create static translations and must include all target languages.

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. To add static translations for each language, open the Translated Notifications tab, and then select New .

5. Select Request Translations , and then select the target languages from the list.

Step 3: Translate and publish content 1. Log in or impersonate a fulfiller from the assigned localization group.

2. Using the filter navigator, go to Localization Framework > My Tasks (sn_lf_task table) and the UI action, Translate .

3. Open each translation task, complete the required fields, and then select Publish Translations .

4. (Optional) To include templates and layouts in your static translations:

Open or create an email template and add translations for each supported language.

Create or select an email layout to match your template.

Note : You can make minor changes to an email that uses a template by overriding the subject line and message body content in the notification form.

Beginning with the Utah release, you can add translated versions in the Translated email layouts tab, and include ${notification:body} in the layout. For more information, see Notification variables.

Step 4: Configure user language and preferences 1. Confirm that each recipient’s Language field (sys_user.language) is set correctly.

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.

2. 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 user Go to User menu > Preferences > Language & region , and then select the preferred language. Step 5: 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 .

Related Links .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: ; } } Multilingual email notifications

Localization Framework support for email notifications Notification variables

Create an email layout

Artifact Configurations.

How to set up dynamic translation for email notifications Email templates

Specific fields show notification content in another language Related known errors:

Cannot request translations to English language

Notification static translations do not work when using email templates

Static Notification should work without any additional step after installing the plugin Fixed in Tokyo Patch 9 and Utah

Email translation is not working if there is no content in the notification trigger Fixed in Vancouver