How to setup static translation on email notifications for first time?SummarySince Tokyo version and onwards, ServiceNow allows both static and dynamic notifications to be sent from the instance. More details about this feature in our documentation page Localization Framework support for email notifications The steps below are intended as and example and general guidance to see how the static translation would work. The steps below are intended as and example and general guidance to see how the dynamic translation would work. Currently Tokyo version is not supporting sending the email digest in the localized form. It is expected that we only send the emails with localized content. Push, SMS and messaging content are not supported for static translation. Additionally, cc and bcc fields as well as meeting invitations are not supported for static translation.ReleaseTokyo and onwardsInstructions1. Once you have upgraded to Tokyo or a more recent version, make sure you have installed the plugin Glide Notification Translation com.glide.notification.translation on the instance. 2. Make sure you have installed the plugin Localization network / com.glide.localization_framework with the languages you want to use in the translations (for example com.snc.i18n.spanish / I18N: Spanish Translations) 3. Check the table system property and create (if it does not exist) the true/false property glide.email.outbound.static_translation.enabled with value = true 4. In the filter navigator, go to the Localization Framework - Settings (table name sn_lf_setting) 5. In the sn_lf_setting table mentioned above, make sure you have or create 3 settings for the three artifacts email_layout_configuration, notifications_configuration and email_template_configuration respectively. In the workflow Preferences tab, select the Localization fulfiller group that would be allowed to create the static translations. the fulfiller should belong to this assignment group and include the languages you would like to allow. 6. Go to the notifications sysevent_email_action table and edit or create a new notification that will have the static translation functionality 7. Select the advanced view 8. You will see a translated notifications tab that will allow you to include the static translations. You can add the translation you need according to your business needs one per language and you require to use the 'New' button to add them: 9. Click on the Request Translations button and select the language(s) from list you added in the step before: 10. Login or impersonate one of the users of the step 5 that belong to the assignment group to publish translations using the filter navigator> Localization Framework -> My tasks (sn_lf_task table) and the ui action "Translate" 11. Complete the required fields and click on Public Translations: 13. (Optional) Open the magnifier glass and select and email template or create a new one 14. (Optional) In the same template created from previous step, create translations for your chosen languages. You can leave them empty if you plan to add layouts as well: 15. (Optional) In the same template created from step 13, select one layout or create a new one 16. (Optional for Utah versions and onwards) Add translations to other languages in the translated email layouts tab and include ${notification:body} in the layout field as the documentation in Notification variables suggests 17. Make sure the recipient language is properly set in the sys_user.language field. Any user which language matches the default system language property glide.sys.language (which is English by default) will not generate translated notifications since source and target languages are the same. For example if sys_user.language is DE (German) and instance system language is DE (German), it is expected that all custom notification content is written in German and having notification translations for users with different languages such as English, Italian, Spanish, etc. 18. Go to the table used in the notification (for example incident, case, task, etc) and make changes in a record to meet the conditions to send an email from the created sysevent_email notification record (for example change the short description, description, etc). 19. The system will create a sys_email record with the message in the standard language 20. You will find a new tab at the bottom called Translated email contents that will show the emails sent on each language. The tab will show records from the sys_translated_email_content table for the specific sys_email record. Translated messages will be included in the sys_translated_email_content table * Optional: If you want to trigger the notification from a flow, you can to change the notification sysevent_email_action.generation_type field (Send when) to the value = "Triggered" Related LinksFor more information about the Languages used in ServiceNow Notification, please refer to our documentation page Localization framework For additional information about email layouts syntax, please refer to our documentation pages Notification variables and Create an email layout To use the Localization Framework to fulfill the translation requests, please refer to Artifact Configurations documentation Links above are part of this feature Localization Framework support for email notifications For dynamic email notification translations, please refer to the KB article KB1156980 How to setup dynamic translation on email notifications for first time? Minor changes can be made on the fly to an email that uses a template by overriding the subject line and message body content in the notification form. That is to say, email body will override the template. More info in our documentation page Email templates Your ServiceNow Tokyo and Utah instances could have this functionality affected by existent product defects as well as other limitations. More details in the links below: KB1539989 Specific fields show notification content in another language PRB1652783 Notification Static Translations do not work when using Email Templates and without sys_translated_notification record PRB1589441 Static Notification should work without any additional step after installing the plugin and translated layout records must be honoured PRB1608509 Email translation is not working if there is no content in the Notification Trigger PRB1766891 Cannot request translations to English language