- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2017 09:04 AM
I have a custom field "U_scheduled_date" in customer Service case table. I need to create an event that needs to be fired before 3 minutes of the date time value in the custom field. I have created an event that is currently being queued but the event always stays in ready state and its not processing. Below is the code i used
var gr = new GlideRecord('sn_customerservice_case');
gr.addQuery('sys_id',current.sys_id);
gr.query();
if(gr.hasNext())
{
while (gr.next())
{
var newdate= current.u_scheduled_date.getDisplayValue();
var gdt = new GlideDateTime();
gdt.setValue(newdate);
gdt.addSeconds(-180);
gs.eventQueue("sn_customerservice.DOB_Update_Case_Sched", gr, gs.getUserID(), gs.getUserName(),gdt);
}
}
Any idea whats the issue here is? Can any of you guys help please?
Thanks,
Tom
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2017 11:26 AM
Hi Berny,
I didn't say this is a constraint. If you look at Toms post you will see that gs.eventQueue is under this form:
gs.eventQueue("sn_customerservice.DOB_Update_Case_Sched", gr, gs.getUserID(), gs.getUserName(),gdt);
The function call is done with 5 parameters out of which last argument value is a date object rather than a queue name. In his screenshot you can see queue contains a date rather than either being empty or containing a specific queue.
Here:
Hope this clarifies your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2017 10:48 PM
Ahh!! Good catch. Indeed. That last argument passed in as gdt shouldn't be considered a "third parameter" been passed in. Instead it could be passed as a parameter instead of the user name.
Something like this:
gs.eventQueue("sn_customerservice.DOB_Update_Case_Sched", gr, gs.getUserID(), gdt);
Thanks,
Berny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2017 08:34 AM
Thanks Sergiu. The issue is fixed now
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2017 08:34 AM
Thanks everyone. Its fixed now
Thanks,
Tom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2017 11:20 PM
Facing the same issue still ... Queue field is empty....
once executed the list of event are not processed and the state always stay as "ready"
Can you please help me out what will be the issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2017 11:23 PM
Queue field is empty for all events that use the regular "events process" job. For other type of events, like text index one which have their own job, the queue will be populated with the defined queue for that job.
So, you mean in your case events are not being picked up by the events process job?