All, What we did, was wrote a little remedy app that keeps track of it.
The way it works is, when ever someone changes a piece of Code (Form, Field, Filter, Active Link, etc.) they put in the project/bug fix it was related too, what their current environment is, a Description of what it was for, and then a date of when it was done. It generates unique Field-IDs for new fields. And in the case where some one makes a whole bunch of changes, you can click a button and it will ask for the login ID and the date to look for from (i.e. I want all the things I changed from 2 months ago to today). Then you can highlight that list and add that into the system. If you just want to look you can have it sorted by Form name or by Project name, to see the code. It came in very handy for us when we had to re-install ITSM 7 for the 3rd time and we had to pull all the changes a Developer had made, but he was out on vacation. We are looking at adding a button to run a report that will list all the code selected and the description of why it was added or changed and throw it into a Word Doc. That shouldn't be too hard as that would just be an OLE call. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Wednesday, October 03, 2007 4:21 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 ** Dear BMC, would that pronouncement include any change that fixes a broken process months before BMC gets around to it? (pause for response, hear only crickets chirping...) Didn't think so. Rick On 10/3/07, Seth Wrye <[EMAIL PROTECTED]> wrote: 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. __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
