Carol, I believe you are getting confused between 'Publishing' and 'Consuming' a web service.
If you generate a web service object on a form, that is making a web service available, or 'publishing' a web service for another system to consume. They would be the trigger, they would consume your web service. If you want to call another system and trigger something in their system, then YOU would be consuming a web service. In this case, THEY provide you with a WSDL, and the filter translates that so you can provide input and output... Based on what you have described above, I believe that you are trying to consume a web service from them to give them an incident id....they would need to provide that wsdl to you. On Wed, Jan 22, 2014 at 1:01 PM, Carol Carnevali < [email protected]> wrote: > I'm sorry, but I'm still having difficulty understanding how you can get a > WSDL from an external application into a Remedy Web Service. I was able to > create a Web Service but Remedy generates the WSDL from the Form selected. > I have also created the filter to consume it but I don't see how it can > work externally. > > What I need to do is simply pass an Incident ID through Web Services to an > external application. > > I'm still missing something and can't seem to find it in any documentation. > > Please advise. > > Thanks. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
