What's the best way to move a ticket in workflow AFTER a specific status change occurs.
I can't be the only one who wants to drop a ticket into the workflow and wait for a specific status to make it move to the next step in the workflow.
Do I have to create a loop with a timer and a condition?
This should be simple.
TjD
Asked by Tim Daugherty
on Wed 2/1/23 2:48 PM
Last edited Wed 2/1/23 2:48 PM
Sign In to leave feedback or contribute an answer
Answer (1)
This answer has been marked as the accepted answer
Mark Sayers
Wed 2/1/23 3:14 PM
Hello Tim,
Essentially yes, that is what you'd have to do to achieve this, short of having iPaaS available to have it find and update a workflow step for you so it gets completed only after iPaaS checks and confirms the ticket's status is the value you're wanting to check for.
Sincerely,
Mark Sayers
Sr Support Consultant
No feedback
The Workflow fails to validate - says I created a loop - which I did ... I want it to check every 30 minutes
- Tim Daugherty
Wed 2/1/23 4:05 PM
You'll need a web service step involved in that loop, where the web service step is just a GET of the ticket (that's the easiest way to alleviate the looping error problem).
- Mark Sayers
Wed 2/1/23 4:07 PM
Mark,
I am trying to do something similar. I essentially want to poll periodically to see if a ticket has a value set, which would by done by a Technician, but might take a few days to a couple of weeks. Once that value is set, the workflow can continue. I haven't set up Web Services. Can an iPaaS flow call do have the same effect? Is there a better way to handle this scenario?
Thanks,
Jim - Jim Lucas Wed 7/24/24 4:05 PM
I am trying to do something similar. I essentially want to poll periodically to see if a ticket has a value set, which would by done by a Technician, but might take a few days to a couple of weeks. Once that value is set, the workflow can continue. I haven't set up Web Services. Can an iPaaS flow call do have the same effect? Is there a better way to handle this scenario?
Thanks,
Jim - Jim Lucas Wed 7/24/24 4:05 PM
You don't really need the web service step to do anything. It can, in all reality, even *fail* to do what it was set up to do, so long as the step is present in the loop, but I'd make it just do a GET on the ticket since that is simple enough to set up and requires no call Body be provided.
So you'd have a Condition to check for status or other field value, a timer to wait 1 operational/actual day, a web service step that does something. Then loop that web service step back to the Condition to do its check again. - Mark Sayers Wed 7/24/24 4:16 PM
So you'd have a Condition to check for status or other field value, a timer to wait 1 operational/actual day, a web service step that does something. Then loop that web service step back to the Condition to do its check again. - Mark Sayers Wed 7/24/24 4:16 PM