So if I can ask ... what did you find in Incident that was really stupid?
On 12/6/07, strauss <[EMAIL PROTECTED]> wrote: > > ** Let's see: > 1. Cut back on the number of BMC applications you buy and install, with a > goal of keeping your object count down. > 2. Buy someone else's application that does the same things with far less > code. > 3. Build your own custom apps and keep the code tighter than a tick. > > I think the custom shops are the ones most likely to suffer a severe > degradation of their work environment if they lose the ability to see > related workflow. Those of us on ITSM just have to suffer, and put the > monkey back on BMC's back to fix all of the broken stuff for us. We found > something really stupid broken in Incident just last week (it's been > released code for HOW long???), and rather than try to troubleshoot it > myself without a search db, I dumped it on them immediately; they had a fix > for it the following day - one that isn't in any patch through 006. I guess > that is the new model for packaged apps. > > Christopher Strauss, Ph.D. > Call Tracking Administration Manager > University of North Texas Computing & IT Center > http://itsm.unt.edu/ > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *T. Dee > *Sent:* Thursday, December 06, 2007 2:03 PM > *To:* [email protected] > *Subject:* Re: Synch Search Database > > > ** Oh this explains why it didn't work for me. > > I wish I could see "related workflow" it would make it easier to trace > things. > > So is there no way around this? > > Thanks. > > __20060125_______________________This posting was submitted with HTML in > it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
