Include Currently Logged-In User's Name and Schedule in Content>>Body HTML in Email Client Template

adityaverma
Tera Contributor
  • TO: should be contact.email

  • CC: should include both the Assigned_to user and the currently logged-in user.

If the assigned user and the currently logged-in user are the same, they should only be added once.
This should be done in the Email Client Template.

3 ACCEPTED SOLUTIONS

Bhuvan
Tera Sage

@adityaverma 

 

You can create a email client template similar to out of box template 'reply-for-customer-service'

Bhuvan_0-1757054622237.png

Below is for sample,

 

Bhuvan_3-1757056360672.png

Sample Case record applied with newly created email client template for testing,

Bhuvan_4-1757056436779.png

If you need to check for unique email ID, better to use email scripts where you create an array and check uniqueness and convert to string and add it to recipients list.

 

If this helped to answer your query, please mark it helpful & accept the solution.

 

Thanks,

Bhuvan

View solution in original post

Ankur Bawiskar
Tera Patron
Tera Patron

@adityaverma 

try to use script in email client template and use script include to handle this, see if that works

Scripting with Email Client Templates 

If my response helped please mark it correct and close the thread so that it benefits future readers.

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

View solution in original post

@adityaverma 

 

This is the behaviour when email IDs are different and confirmation email ID uniqueness logic is handled out of box by email client template

Bhuvan_0-1757058007476.png

If this helped to answer your query, please mark it helpful & accept the solution.

 

Thanks,

Bhuvan

View solution in original post

11 REPLIES 11

Mark Manders
Mega Patron

Why would you want to send the email to the person creating the email? They know what's in there, right? And they have access to the record they are emailing from, so they have it also in that ticket.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

it is the requirement. 🙂

That's the worst kind of explanation. You should never develop anything of which you don't know the why. And 'it's the requirement' is not a 'why'. 


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

If the requirement comes from the client, then we have no choice but to follow it. A requirement is a requirement — it's not appropriate to say things like 'That's the worst kind of explanation.' That's why I shared my thoughts in the community. Please be polite.