Javascript parsing in email client template not working on 'code symbols ,' '<' '>' - Known Error

Javascript parsing in email client template not working on 'code symbols ,' ' ' Description Javascript in email client template fails parsing on comma, less than, greater than in code.

Steps to Reproduce

1. Create a new email client template for the incident table with the following code in the CC field:

javascript: if (current.short_description.startsWith("test")) { recipients="testemail@somwhere.net"; } else { var watcher=new GlideRecord("sys_user"); watcher.addEncodedQuery("sys_idIN" + current.watch_list.toString()); watcher.query(); var watchlist_email=""; while (watcher.next()) { watchlist_email=watchlist_email + watcher.email + ";"; } watchlist_email=watchlist_email + current.caller_id.email;

var watchlist_str=current.watch_list.toString(); var watchlist=watchlist_str.split(","); for (j=0;j if (watchlist[j].indexOf("@")>0) { watchlist_email = watchlist_email + ";" + watchlist[j]; } } } recipients=watchlist_email; copied=watchlist_email; }

2. Save the record.

3. Open any existing incident record.

4. Add a few users to the watch list.

5. Click on the email client icon and check the CC list.

The email client will show the code following one of these characters (comma, less than, greater than) in the address field, rather than evaluate the complete javascript and execute returning the result.

Workaround After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience.

Possible workarounds:

Scripting might not be necessary if the the goal is to include users contained in a field on the target record. If that is the case, set the value of one of the recipient fields to a comma separated list of field names. i.e. "watch_list,caller_id,assigned_to".

For templates containing scripts with commas in it, move the script to a Script Include and call the script include from the client template.

For the case where a script returns comma separated fields, for example when trying to return "watch_list,caller_id", the only option would be to put the caller_id in the watch list. Related Problem: PRB1250372