Notification variable not getting translated

[Kevin Paul]

Hi,

For translation of notifications, we have created notification in each language(french and english). For one of the french notifications, there are variables added in the message body. This notification is created in the sc_request table.

I have changed the language of the recipient to french in the user table and as well as changed the language in profile to french. Look at the image below, the ui is now in french. The field impact's value is translated here.

However when the notification is triggered, you can see the word, 3 -Medium is not translated. The same word is translated as 3 – Modérée in the above image, which is taken from the sc_request table from which the variable is used in the notification record.

How to fix this and translate that variable's value. The translated value is already available in the sys_choice table, but why it does not appear in the notification still remains unclear (language is set to french both in the user table and in the preferences table) .Any workaround/help is appreciated.

Thanks in advance!

[Alex Coope - SN]

@Kevin Paul 

Just looking through the thread and catching up, 

If I've understood all the different screenshots correctly ${impact} is a field defined on the task table (I'm assuming it's the OOtB field actually) rather than a variable (it's an important difference, especially in notifications. I very nearly started talking about the [question_answer] table to answer why some calls do appear to show their translations and others don't),

As others have suggested, the current way to obtain a choice in the language of the intended recipient (currently at least), is via a mail_script to essentially fetch it via a GlideRecord query. I can't talk about the future, however I can say (as a team) we're discussing this very topic at the moment,

As with most notifications and their designs, it comes down to UX (User Experience) best practices. Meaning, do you really need to present a whole bunch of information in the email notification? Or could you keep it super simple like:

"Your [record] has had an update, click here to find out more"

where that link takes the user to the portal to see everything they need to see. This also serves as a good traffic driver to the portal if that's what the business is aiming to achieve,

So food for thought,

Many thanks,
Kind regards

[Kevin Paul]

Thanks Alex! As you have talked about the difference btw variables and OOTB fields in notification. How to find the difference between them?

[shloke04]

Hi @Kevin Paul 

In above post of your when you say transalated value is available in sys_choice table, can you confirm if both Label and value of the choice is translated and available.

Can you share a screenshot of that particular choice value here and also when you are fetching the value of Impact in your script to add it to your Notification , can you fetch the Display Value of it and I believe that should resolve this issue.

Something like below:

object.getDisplayValue('impact');

Can you share more details to assist you further here.

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

[Kevin Paul]

[Kevin Paul]

I did not use any script to fetch the impact value in the notification. I used ${impact} only