If you are asking our opinion of the strategy, I am opposed to it. Services are the what, not the how. I might add that management requirements should be the same. Tell me what you need, and let me figure out how.
If they want to track this via Services, create one or more that describes the generic function being performed for the customer. Making them customer specific leads to an out of control service catalog. Rick On Apr 3, 2014 5:45 AM, "Pierson, Shawn" <shawn.pier...@energytransfer.com> wrote: > ** > > Good morning, > > > > We got a new requirement this morning of setting up web services as CIs so > they can be tied to Change Requests as well as provide our I.T. security > department a list that they can maintain and monitor. Mostly we would need > to just track the name, a URL, and some attribute for marking it as being > available outside the network. There are a few different classes that I > could see potentially using but since there isn't one that is marked > specifically for it I wanted to see where you all would suggest tracking > them. > > > > Thanks, > > > > *Shawn Pierson * > > Remedy Developer | Energy Transfer > > > Private and confidential as detailed > here<http://www.energytransfer.com/mail_disclaimer.aspx>. > If you cannot access hyperlink, please e-mail sender. > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
