Email layout translation doesn't work

[Thomas Mueller2]

Hi,

Followed this guide: https://www.servicenow.com/community/international-localization/static-multi-lingual-notification-su...

I have a customer where we are utilizing the Glide Notification Translation (Static only!).

Translating the notifications' body is fine as I verified in the logs.

As we are now forced to use a single email template I thought I could easily translate the layout itself as I did for the notification body.

Sadly this doesn't work and I seem to be not the only one having the issue:

https://www.servicenow.com/community/now-platform-forum/how-to-enable-translated-email-layouts-templ...

https://www.servicenow.com/community/international-localization-forum/email-layout-is-not-translatin...

Dynamic translation is not an option.

Is this something to be fixed in Vancover release or is there something I am missing out?

[Alex Coope - SN]

@Thomas Mueller2,

So there should be an artifact called "Email Template Configuration" in Localization Framework > Artifact Configurations. Meaning, you may need to create a "setting" for this artifact if you don't have one that applies to all artifacts.

This artifact runs against the [sysevent_email_template] table, which is where it would be requestable from once the setting is defined. Here's a screenshot from a demo template called "Employee Notification Template":

^ note that anything in ${} calls would be calling objects from the triggered notification itself, so be very mindful of how that text is structured. Meaning, if you have field labels, choices etc you may need to leverage a mail_script in order to collect the translated version of them.

Ultimately, templates have been translatable via the Localization Framework since the Tokyo release (same time Email's were introduced),

Many thanks,
kind regards