Number not being displayed in incident assigned to me email

Sharique Azim
Kilo Sage

Hello,

We are seeing this issue where the number is not being displayed instead we are seeing 

{number} was recently assigned to you.

I am sure the issue is with the notification script "incident_assigned_to_you"

 template.print(sn_i18n.Message.getMessage('global',
        "{html0}{incidentNumber} {html1}{html2}was recently assigned to you.{html3}", {
            "incidentNumber": "${number}",
            "html0": '<div style="font-size: 16px;" ><span style="font-weight: 700; color: #181A1F;">',
            "html1": '</span>',
            "html2": '<span style="font-weight: 400;">',
            "html3": '</span></div>'
        }));

 where probably, the script is not being emulated properly.

Just an FYI, we do not have translation enabled in our instance.

 

Please suggest how to fix this?

 

Thanks,

Shariq

1 ACCEPTED SOLUTION

oster
Tera Guru

We had the same issue after Yokahama upgrade. Replacing the ${number} with current.number works as work-around.

View solution in original post

14 REPLIES 14

@Sharique Azim 

did you try including this email script in a custom notification on incident table and see again if it shows correct?

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

oster
Tera Guru

We had the same issue after Yokahama upgrade. Replacing the ${number} with current.number works as work-around.

LaurentK
Tera Contributor

Same issue here also after Yokohama upgrade, with translations enabled.

Thank you for the current.number workaround; very helpful ! Just to be clear for other readers, you want to get rid of the double quotes as well. Like this:

"incidentNumber": current.number,

 

Vishal Jaswal
Giga Sage

@Sharique Azim Thank you for sharing this and interesting to see there are others facing the same issue.

 

can you post the screenshot of stats.do so that I can compare my yokohama update version with yours and if possible can you patch it with latest hotfix.


Hope that helps!

Ours has the issue with:
Build name: Yokohama
Build date: 04-30-2025_1345
Build tag: glide-yokohama-12-18-2024__patch3-04-17-2025