That would be another way of doing it, but it would still mean multiple WSDL
calls in case of multiple CI's per incident.. They would still be all simple
WSDL's..
Joe
-----Original Message-----
From: Grooms, Frederick W
Sent: Monday, October 22, 2012 6:03 PM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: Re: complex web services 7.6.03
You should be able to as long as you can tie between the Incident and the CI
using a single field (You might have to create a Join form in Remedy)
Fred
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Joe Martin D'Souza
Sent: Monday, October 22, 2012 4:51 PM
To: [email protected]
Subject: Re: complex web services 7.6.03
**
Rick,
The simple answer is that in one call no.. You may be able to circumvent it
by two (or more depending on the number of CI’s) WSDL calls to achieve what
you want to..
Remedy can send and receive simple WSDL’s that do not use any complex
constructs (the integration guide talks about this under the web services
section).
Joe
-----Original Message-----
From: Rick Phillips
Sent: Monday, October 22, 2012 5:27 PM
Newsgroups: public.remedy.arsystem.general
To: [email protected]
Subject: complex web services 7.6.03
**
Hi, everyone,
I have a requirement that must use web services. I need to create a WSDL
that will send an Incident form from one system to another (also, 7.6.x),
but the (single) WSDL must include any related CI's. Is Remedy's complex
web service capability that complex? Can it be done?
tia,
Rick
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
