gs.eventQueue not firing properly

patricklatella
Mega Sage

Hi all,

I'm building a scheduled job to fire an event, and am using the following script, however in the line in BOLD the script is giving me the error in the screen shot...it's not firing the event properly and my notification that is triggered off that event is not sending.   Error in my script?     thanks!

var sd = new GlideRecord('change_request');

sd.addQuery('state','-5');

sd.query();

while(sd.next()) {

if(gs.dateDiff(gs.nowDateTime(),sd.end_date.getDisplayValue(), true) < 0)

gs.eventQueue('change.notification', sd.number, sd); //something wrong here?

}

find_real_file.png

1 ACCEPTED SOLUTION

Michael Ritchie
ServiceNow Employee
ServiceNow Employee

Your second parameter needs to be a record.   See this Wiki article for details:


GlideSystem - ServiceNow Wiki



3.1.1 Input Fields

Parameters:


  • Name of the event being queued.
  • A GlideRecord object, such as "current".
  • An optional parameter, saved with the instance if specified.
  • A second optional parameter, saved with the instance if specified.
  • An event queue to add the event to.


So the following should work:


gs.eventQueue('change.notification', sd, sd.number);


View solution in original post

19 REPLIES 19

patricklatella
Mega Sage

excellent thanks Michael.   And one more question...do notifications fire in the developer instance?   I know that wouldn't actually send an email, but would notifications that should be sending show up in the System Logs > Email?   Just to verify that my chain from scheduled job > event >notification is working.


You should be able to see them in the Outbox, if email hasn't been configured.


patricklatella
Mega Sage

hmm...not seeing any record or my notifications sending.   Here's my "when to send".   And "change.notification" is my event...do I have that correct?



find_real_file.png



find_real_file.png


patricklatella
Mega Sage

here's my event firing, but nothing in the Outbox


find_real_file.png



find_real_file.png


hum...   It seems that your event hasn't been processed. Are you sure your events process is processing events in your instance, or that you schedule job was set to run the job at a later stage, and that time hasn't come ?