Re: WSDL's two questions

[Sam Ferguson]

Title: Message

** 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 If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail.     http://www.ml.com/email_terms/ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___