- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2018 03:35 PM
Experiencing issues with an email notification firing off. The expectation is that all recipients are in the BCC field.
The email (watchlist) recipients are all BCC via an email script and the the email is event driven via a scheduled job. The email notification only seems to fire when I insert a user recipient into the notification. An email is generated with the recipient and the watchlisted users in the BCC field.
However when there is no user specified in the notification and only the "Event Parameter 1" referencing the watchlisted users from the scheduled job, the email will NOT fire. What am I missing? Thanks in advance.
Solved! Go to Solution.
- Labels:
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2018 08:44 PM
Have you considered sending the notification to your-instance-name@service-now.com, adding your parm1 to BCC using Notification Email Script and setting up an inbound action to ignore emails from your instances SMTP account? May not be the exactly what you are looking for, but this should work.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2018 08:11 PM
Maybe try setting 'send to event creator'. Is event parameter 1 user the person who triggered the notification?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2018 08:44 PM
Have you considered sending the notification to your-instance-name@service-now.com, adding your parm1 to BCC using Notification Email Script and setting up an inbound action to ignore emails from your instances SMTP account? May not be the exactly what you are looking for, but this should work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2018 03:02 PM
Thanks, I'll have to try that. As a temporary measure I wound up inserting a dummy "do not reply" user account to insert in the To field.
I also tried adding a prefix to the subject line and used the email properties for inbound actions to ignore email with that prefix (though I believe the "RE:" being inserted before the prefix is preventing this from working.) I hadn't considered using an inbound action to accomplish this, thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2021 04:10 AM
It worked for me.