
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-05-2018 09:28 AM
OK, so I have trolled a bunch of threads about this particular topic (there are a ton) and still can't resolve my problem. I'll include screen shots of my configuration below. I have a scheduled job that runs a query and calls an event for each record returned. I can see from the notification related list on the event log entry that there is no attempt to send a notification. I have verified that all intended recipients have valid emails and are receiving other notifications. Other notifications are firing in this instance as configured, so no issues there. I'm hoping I'm just missing something small. Thank you in advance for your help!
Note, I have tried calling the gs.eventQueue() two ways in my scheduled job.
- gs.eventQueue("EVENT_NAME",OBJECT,PARM1,PARM2)
- parm1 = email address of intended recipeient / parm2 the number of the associated record.
- (This can be seen in my screen shot of the event log.
- gs.eventQueue("EVENT_NAME",OBJECT)
IMAGES -
- Event
- Scheduled Job
- Notification
- Event Log
- Event Record
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2018 09:58 AM
Domain for the win. The table that was being referenced was not "in a domain" or domain separated, thus all the records were in global. The notification was in a subdomain and, as a result, would never fire. I moved the notification to global and everything is behaving sending just the object to the event, no params.
gs.eventQueue("eventName","object");
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-05-2018 10:12 AM
Hi Mike. I'm not an expert on this but I have been through some of my scheduled jobs to compare and in all instances parm1 and parm2 are always set to the UserID and UserName:
gs.eventQueue("quote.expiring", gr , gs.getUserID() , gs.getUserName());
Script:
var gr = new GlideRecord('u_order');
gr.addQuery('u_quote_status', 'provided');
gr.addQuery('u_quote_expires','>',gs.daysAgo(-4));
gr.addQuery('u_quote_expires','<',gs.daysAgo(-6));
gr.query();
while(gr.next()) {
gs.eventQueue("quote.expiring", gr , gs.getUserID() , gs.getUserName());
gr.update();
}

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-05-2018 10:23 AM
Wayne, are these scheduled job / event combinations designed to send a notification? I'm not sure how the sys_id and user name of the logged in user would allow for that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-05-2018 10:44 AM
Yes, I have two notifications triggered by this event. One for the Customer and one for the Watch List. Both are set to 'Send to event creator' and neither have Event parm 1/2 checked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-05-2018 11:05 AM
There's a very good chance than neither of those fields does anything, I simply copied them from another notification that was doing something similar. However, the scheduled job, event and email notification are all doing their jobs.