1 of 1 people found this helpful
So, if you analyze the timings of workflow when running resolution on non-integrated vs integrated tickets, you will likely find the only difference being that web service call. You have a few options in this scenario.
1 - Continue along as you are (not your preferred option of course)
2 - Create an 'interface' form that contains all of the information that you need for the integration, and instead of performing the integration directly from your ticketing form, perform a push into this form. Then, you could have an escalation come through and take these records that are in that form and process them properly.
The down side of option 2 is that the integration is slightly deferred, you can have the escalation run once a min (might want to run in it's own pool), but if that's not an issue for you, then it might be the best option that I can think of
There are a few alternatives you could try if neither of those work, but they are significantly more 'advanced' and might not be needed if you are ok with the slight deferral
One thing I try to get people to think about when doing an integration as part of a record update (either pushing or pulling data with another application), is that the other application's processing time for the transaction now becomes part of your update processing time.