Web Service Step Completion
Hello,
I was looking through the documentation but couldn't find an answer to the following question - A Web Service Step in a workflow will always wait for a response, be it a successful 200 code or any other information, from the server before the workflow continues, correct? The success or failure branches are only activated once the workflow receives a response from the queried server? Asking because we'd implemented timer steps after our Web Service steps to make sure information was returned, but I'm wondering if those are now needed.
Thanks!
Trent Urness
TDX Platform Technician
University of Minnesota
Answer (1)
Hello Trent,
Yes, the web service step always waits for the response from the server before it is marked as completed by the workflow. That means whatever action the web service step was supposed to take either A) has indeed been completed by the time the step is marked completed or B) could not be completed, but one way or the other the server has identified that the step did complete with a Success/Failure message.
There's really no need to wait any additional time after a web service method step to ensure that they did complete, unless you for sure need to make other calls and want to make the system wait 5-10 minutes to ensure they run on a different processing sweep than the most recent call.
Awesome! Thank you for the info, that answered my question perfectly. - Trent Urness Wed 4/13/22 3:30 PM
We recently built a process in our 3rd party platform called Boomi that TDX reaches out to via a Web Service Step as part of a workflow. That process collects the ticket information, makes a few API calls for itself, and then sends a Patch API to the TDX ticket before sending a 200 code back to the ticket.
We're seeing an error where the in the ticket, the Web Service workflow step resolves before the information from the Patch API is recorded in the ticket. This is unexpected because the ticket cannot get the 200 code until the Patch API has completed in our Boomi Process. Adding a timer after the Patch in our Boomi process doesn't change this behavior. Adding a timer after the Web Service Step in the workflow also does not change the behavior, but the wait step allows for the workflow to not move forward before it records the Patch changes. So it looks to us like it is not waiting for the 200 to continue in the workflow - can you explain what's going on here? - Trent Urness Tue 4/25/23 10:34 AM
Wait step added in the workflow, still doesn't wait for the Patch, but the wait allows the step to take time for the Patch to go into effect - https://tdx.umn.edu/SBTDNext/Apps/29/Tickets/TicketDet?TicketID=1021541 - Trent Urness Tue 4/25/23 10:36 AM