Rakshit, In v7.1 there should be a way with Filter error handling. (But I have not yet tested this new feature.)
In versions prior to v7.1 you would need to choose to not use the "standard" way to call a web service and instead opt to build a way to call the web service. Maybe a Java Scripting plugin or a command line call... or some other "older style" integration technique that could encapsulate the Web Service conversation and "do the right thing" to never produce an error that the ARS server would see. But I think it would be generally easier to upgrade to v7.1 and test out the new feature than to develop your own "alternate integration method" that you likely would want to abandon after you complete a future upgrade to v7.1. HTH -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 10/29/07, Rakshit Bhandary <[EMAIL PROTECTED]> wrote: > ** > Hi, > > In Remedy, when we call a web service of other application and if that > webservice is down for some reason, we get a error on the user end or on > server end depending on how the qworkflows are designed. What i wanted to > know is, is there a way to capture this kind of error as a exception and > take some other route. > > In my case, our application has a form where records are there. There is a > flag in this form to suggest firing of that record through a web service to > another application. I set that flag through a escalation Push Field action. > The problem occurs when that web service is down and escalation queue gets > held up and brings down the server. Is there a fall back mechanism? Kindly > advice. > > ARS 7.0.01/Sun OS 5.10/Oracle DB 9.2.0.6 > > Regards, > Rakshit _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
