The two scripts should be in separate e-mail scripts. To clear up things, even if several e-mail scripts are included and executed while an e-mail is generated, those all share a single session and global object. That is why a global variable set by one e-mail script, will be available to all e-mail scripts executed after it. Also to clear things up, those variables that are defined outside the default IIFE (
(function runMailScript (current, template, email, email_action, event) {
})(current, template, email, email_action, event);
) all become global variables.
So if one writes:
(function runMailScript (current, template, email, email_action, event) {
var i = 0;
})(current, template, email, email_action, event);
i will not be a global variable, because it has been defined inside the IIFE. It will only be available inside the IIFE. However if one writes:
var i = 0;
(function runMailScript (current, template, email, email_action, event) {
})(current, template, email, email_action, event);
i will be a global variable, because it has been defined outside the IIFE. It will be usable not only in the "current" e-mail script, but in all e-mail scripts that will be executed after it. Actually it will be available in all e-mail scripts, just that in e-mail scripts executed before it, the variable will be undefined.
Back to the e-mail script to get the current e-mail's language, it is just an example, the important bit is that it sets global variable u_translationLanguageCode. It loads a user record and reads and returns the preferred_language field, or if the user record could not be loaded, it will fall back to the session language. You will need to write your own script to determine the correct language, whether in a reusable e-mail script or in all e-mail scripts. B.t.w. you could also move the code to determine language into a Script Include and later call it in all e-mail scripts that need it, but in that case you will be calling the same code multiple times for no reason. But it might be safer.
But how exactly would you know which user to load, I don't know, it depends how the recipient is set. Is it the Requested for user? Is it someone in the Watch list field? Or an arbitrary user? Only you can tell :-). But the bottom line is, you need to find that use in the user database and put the value in field preferred_language into a global variable (u_translationLanguageCode). Of course, you can name your global variable anything you'd like - but you should use the u_ prefix to make it less likely to collide with other SN global variables. I suppose I could be more precise in what script you need to right to set the global language variable, but you need to tell us how do you determine the recipient here.
Finally the script that I posted above could be written as below too:
var u_recipientUniqueValue = u_getRecipientUniqueValue();
var u_translationLanguageCode = u_getTranslationLanguageCode(u_recipientUniqueValue);
function u_getRecipientUniqueValue() {
// This needs to return the recipient user's sys_id
}
function u_getTranslationLanguageCode(sys_user_uniqueValue) {
var sys_user = new GlideRecord('sys_user');
return sys_user.get(sys_user_uniqueValue) ? sys_user.preferred_language + '' : gs.getSession().getLanguage();
}
Just that here I no longer employ an IIFE, thus I am polluting the global scope with unnecessary variables like u_recipientUniqueValue, u_getRecipientUniqueValue and u_getTranslationLanguageCode which don't need to be there.
