Lucky for me I can use a simple Filter Run-If of $SERVER$ LIKE "dev%" ( or "tst%" or "prd%"), but you are correct that it would be great to be able to override the target URI.
One problem I keep running across is the unique key for sub forms. i.e. Using the Purchase Order example, we have no line item number in the data that is coming in to Remedy since all we do is a create into Remedy of the data. Requiring a unique key is a pain to have to have a dummy optional field and filters to null it out on submit, modify and merge. Another problem is that I can't use a sub-form more than once. i.e. In telecommunications we have to know (among other things) who at the site is the contact person as well as who is the technician being dispatched. We store this type of information in a sub-form with a Contact Type identifier. In order to send this info thru web services I have had to make db views for each type and Remedy view forms on them just to be able to do the mapping. Fred Grooms From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of LJ Longwing Sent: Friday, May 08, 2009 9:38 AM To: [email protected] Subject: Re: Webservices 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 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
