Does it count if I don't like how the target URI isn't data referenceable?....by this I mean that when I consume an external web service, I need to point my Dev, Test, and Prod to different URIs. This means that I either can't have the same workflow in all environments, or I need to develop a complicated data driven structure (which is what we have done here) that determines which filter to fire based on what environment we are in, and have as many copies of the filter with the same workflow, but different URIs as I have environments. This is the biggest hurdle I have had to face in regard to Remedy's implementation of web services.
_____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Axton Sent: Friday, May 08, 2009 8:27 AM To: [email protected] Subject: Webservices ** I wanted to get a feel from the group on some of the headaches and limitations of the Remedy web services implementation. I've avoided the interface, much like the palgue, since it was first adopted. I'm looking for limitations when people interface bi-directionally with other applications, performing operations like creating incidents, in relation to things like not being able to support certain data types, not being able to query certain outside webservices due to how they are structured, etc. Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
