I would think that was a statement is only to discourage customers from being too adventurous in their efforts to customize the products. That would result in fewer support calls of the nature wherein someone calls in and complains - "Hey I did this and this is what happened instead of this - how do I....."
Small changes here or there that might add a new functionality OR disable an existing one which isn't a core functionality because its not needed or necessary, should be ok so far as these changes have been documented using various methods that were described earlier in this thread. The bottom-line is that while upgrading, there should be minimum interference between changes made and the new definitions that would be imported into the system. That statement you heard was perhaps a disclaimer to customize at your own risk.. I personally discourage customers using ITSM 7 from any major changes myself. My argument usually is the cost of upgrades upon heavy customization. The value of changes over the cost of the product is also a good argument to use. If you have paid as much as you have for a Rolls Royce, why customize it to look like a Mercedes. Why not buy a Mercedes in the first place.. There is a risk to every change - what drives certain changes however is the value brought by that change over the cost of the risk for implementing that change.. If that value is not worth the cost of change, the change is obviously not worth it.. Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Seth Wrye Sent: Wednesday, October 03, 2007 5:10 PM To: [email protected] Subject: Re: What is everyone doing to keeping track of created Forms/AL/Filters...ect from out of the box ones As I was told in my most recent CMDB training class from the instructor, "Any change to the OTB product is a bad change". Now that made me shudder... I wonder if the OTB products will eventually be locked apps? Seth ________________________________ From: Action Request System discussion list(ARSList) on behalf of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Wed 10/3/2007 4:56 PM To: [email protected] Subject: Re: What is everyone doing to keeping track of created Forms/AL/Filters...ect from out of the box ones Matt's is a very good suggestion. The very big pitfall that always lurks is when an OOB workflow object becomes something(s) else due to a BMC patch or upgrade. For example, suppose you have an OOB Active Link named OOB:ActiveLink1. Using a prefix, you create your "custom" version of the object and disable the original. So now you have OOB:ActiveLink1 and, say, New:OOB:ActiveLink1. But now BMC decides OOB:ActiveLink1 will now be "enhanced" to become OOB:ActiveLink2 and OOB:ActiveLink3. In other words, to add functionality, they replaced the original AL with two (or more) new ones that are named differently. Now you have: New:OOB:ActiveLink1 OOB:ActiveLink2 OOB:ActiveLink3 When you should only have (if you had never jumped off the cliff and customized the OOB product): OOB:ActiveLink2 OOB:ActiveLink3 Now you have workflow whose names are not consistent that are likely performing duplicated and/or extraneous actions. Makes one shudder at the thought of upgrading... Norm -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Wednesday, October 03, 2007 3:34 PM To: [email protected] Subject: Re: What is everyone doing to keeping track of created Forms/AL/Filters...ect from out of the box ones I am a big fan of packing lists for development processes. I would suggest that you create at least two packing lists. A) OOB objects that were replaced/changed/disabled and B) New objects that were added to the OOB Those two lists would give you a shot at being able to detect how your changes play out in the "new version". (After the install of the upgrade/patch you view those packing lists and see if any of the objects were changed during the install/upgrade. If so, then they require very close review.) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.14.0/1046 - Release Date: 10/3/2007 10:08 AM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
