- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 09:53 AM - edited 05-25-2023 09:54 AM
Dear Experts,
I have a catalog item called Miscellaneous:
The issue is that the delivery task is not always triggered by the workflow, even though it is using the same workflow for every order. This causes some tickets to remain open even though the workflow shows that they are completed.
Sometimes workflow is completed as seen "close by" with the technician name, and sometimes workflow is not triggered so the close by remains empty., because the workflow was not triggered. Not sure what is causing this. Please Help.
same workflow, but different results.
Thank you, appreciated.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 09:57 AM - edited 05-25-2023 10:03 AM
Has the "Wait for completion" been unchecked from the Delivery task? It's possible the workflow is reaching the end prior to all task being closed.
We end ALL of our workflows the same way...with a script that checks and waits for any open tasks to close and then the workflow moves forward once all tasks are closed and the workflow then closes.
This is the Wait For Condition script:
var g= new GlideRecord('sc_task');
g.addQuery("request_item",current.sys_id);
g.addQuery("active",true);
g.query();
if(g.next())
{
answer=false;
}else{
answer=true;
}
Please mark this response as correct and/or helpful if it assisted you with your question.
Steven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 09:57 AM - edited 05-25-2023 10:03 AM
Has the "Wait for completion" been unchecked from the Delivery task? It's possible the workflow is reaching the end prior to all task being closed.
We end ALL of our workflows the same way...with a script that checks and waits for any open tasks to close and then the workflow moves forward once all tasks are closed and the workflow then closes.
This is the Wait For Condition script:
var g= new GlideRecord('sc_task');
g.addQuery("request_item",current.sys_id);
g.addQuery("active",true);
g.query();
if(g.next())
{
answer=false;
}else{
answer=true;
}
Please mark this response as correct and/or helpful if it assisted you with your question.
Steven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2023 07:23 AM
Thank you for your help.
Appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 10:58 AM
I will try this one. Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 11:35 AM
Wait until the condition is active,
Once the inbound reply is true the delivery task is triggered.
however, sometimes the delivery task is assigned to tech, other times it will end the RITM itself leaving it as an open ticket.
As stage shows it task was created but it moves itself to the end without generating task for technician to close the ticket.
as you see it wait for the condition to be True then it create a Catalog Task, but it will not trigger for Tech, and it automatically goes to end but does not close the ticket
Sometime it work sometime it does not. very confusing.