Fred:
I want one too!!! I'm investigating the use of XML/Web Services vice DSO for a particular project (no I cannot go into details.)
James McKenzie
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W
Sent: Monday, May 08, 2006 11:35 AM
To: [email protected]
Subject: Re: WSDL's two questions
Chris,
Did you remember to look this up?
Did ya, huh, Did ya (I sound like a little kid looking for a present <grin> )
Fred
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Chris Woyton
Sent: Tuesday, May 02, 2006 6:20 PM
To: [email protected]
Subject: Re: WSDL's two questions
Just a quick note on this...
The Web Services Filter Set Field Action is actually executed by a plugin. You can consume a Web Service by calling a Filter API and passing in about 12 different parameters that you can set through workflow. I don't have them handy at the moment, but when I get to my home machine this weekend, I'll supply them to the list.
It's pretty neat what you can do with it. You can build Web Service consumption dynamically, including changing the return mapping. :)
-Chris Woyton
________________________________
Sam Ferguson <[EMAIL PROTECTED]> wrote:
Mike, I don't have any options for your first issue of loosing the mappings. Sounds like an enhancement request to BMC Remedy!
However when it comes to migrating workflow, I have found it rather easy to change the URL in the definition file before importing to the target server. If you export the definition as XML rather than def then you can just change the WSDL URL without having to worry about string lengths which the def file enforces. Not a complete solution, but it may be helpful.
Sam
________________________________
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ilmer, Mike (GTI)
Sent: Wednesday, 3 May 2006 9:27
To: ARSList
Subject: WSDL's two questions
Hello List,
Does anyone have any recommendation on mapping procedure of the new fields for the (outbound) WSDL interface.
It seems like every time when we need to add a new field to the
client's (external) WSDL where remedy needs to push data to, I can see
new fields only after clicking the "Load" button. But, clicking this button causing losing existing mapping. Any recommendations?
Also, any recommendation on migrating the WSDL related workflow form dev to qa to production? The WSDL's url is hard coded and I have two option.
One: to keep the separate workflow for each server. The other option is to modify url before or after each migration. Both options doesn't look really convenient. Any thoughts?
Thanks,
Mike
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
