Target empty / email not shown in activity log when sent using Reply/Reply all/Forward buttons

emaasalmi
Kilo Sage

I noticed that the emails sent (outbound) using the Reply/Reply all/Forward buttons found in the activity log of a ticket are not shown in the activity log. This is probably because the Target field of the email in the email log is empty. If an email is sent using the Email Client (under three dots on the upper right corner) is used, the emails are shown correctly in the activity log and the Target matches with the id of the ticket the email was sent from.

This is quite confusing as the users can't see if the email was actually sent or not, nor can they see the previous conversations.

Has aynone else experienced this? To me this seems like a bug.

 

1 ACCEPTED SOLUTION

They can be enabled by creating a system property glide.ui16.emailStreamResponseActions (in UI16). Once enabled, these buttons appear:

find_real_file.png

 

Anyhow, googling with "glide.ui16.emailStreamResponseActions" got me to this Known Error article I wasn't able to find earlier. So it is indeed a bug:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0684027

 

Also just found another community thread about the same issue with a link to the fix. Weird I wasn't able to find these earlier:

https://community.servicenow.com/community?id=community_question&sys_id=18dd47e1db4f17845129a851ca96...

View solution in original post

6 REPLIES 6

palmen
Tera Guru

What are these Reply/Reply all/ Forward buttons you refer to? In the activity log I don't have these options. Or is it something else you mean?

They can be enabled by creating a system property glide.ui16.emailStreamResponseActions (in UI16). Once enabled, these buttons appear:

find_real_file.png

 

Anyhow, googling with "glide.ui16.emailStreamResponseActions" got me to this Known Error article I wasn't able to find earlier. So it is indeed a bug:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0684027

 

Also just found another community thread about the same issue with a link to the fix. Weird I wasn't able to find these earlier:

https://community.servicenow.com/community?id=community_question&sys_id=18dd47e1db4f17845129a851ca96...

Good to know, didn't know about this property

Took me 3 hours to find it but as soon as I read your post the issue was resolved within about 10 minutes.

Thank you.