Well said Rick.. Maybe their product managers motto is "Happy are thou who believeth in us and have not customized your applications for thou will haveth the benefits of applying our patches. The rest of you please pray real hard before you do."..
I think the best you could do is install P6 on a test/dev server a few days after you install ITSM with P5 so there is a noticeable difference in timestamp on the objects. Then manually wade through all the newly modified pieces of code by the last modified date, and then try figure out what they tried fixing by comparing the prod or QA to the test/dev server.. It might be real hard to find out changes on forms if that has been changed. Will be a project by itself to undertake this activity, but that's the best you can do if BMC is not going to release a fully functional release document for reasons best known to them.. Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Rick Cook Sent: Wednesday, November 07, 2007 9:48 AM To: [email protected] Subject: Re: OT: ITSM 7.0 - Patch 6 ** Michael, maybe your boss will allow you to introduce a blind patch on your dev server, but mine won't, and I wouldn't do it if he did. Maybe BMC should stick to the ITIL rules regarding Release management, so that we can stick to them in Change Management. Also, I remember Doug talking a couple of years ago about the ardisable utility, but I never saw it actually available - I thought it was just another idea he threw out that turned out to not be released to us. Is it on the Dev. Network or somewhere? Rick ---------------------------------------------------------------------------- -- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Michiel Beijen Sent: Wednesday, November 07, 2007 12:23 AM To: [email protected] Subject: Re: OT: ITSM 7.0 - Patch 6 ** I hear you... What I would recommend is of course running it first on a dev/test environment. You could create a user with a name like 'ITSM7Patch006' to run the installer with. This way it is pretty easy to see which workflow and fields have been touched by the installer. If you have sticked to the 'rules' which Doug Mueller set some time ago (ref: http://www.remedy.com/corporate/ron/volume02_issue01/english/article_03.htm ) and use the ardisable utility you can do a patch upgrade pretty fast. Of course it would also be nice if BMC would just add a list with touched fields and workflow in their patch... -- Met vriendelijke groet / Kind regards Michiel Beijen ______________________________________________________ MANSOLUTIONS Energieweg 60-62 3771 NA Barneveld The Netherlands Tel. +31-(0)612968592 Mail [EMAIL PROTECTED] Internet http://bsm.mansolutions.nl On 11/6/07, T. Dee < [EMAIL PROTECTED]> wrote: I don't understand Remedy - I have run into issues with Incident and have reported them to Remedy. Remedy has identified them as known errors (SW00249109,SW00262080,SW00263933). I can not find these on their support web site. I'm told that Patch 6 will fix these issues. However, i'm also told they don't know nor do they have any documentation as to WHAT workflow they touch / update. This I don't understand - there are alot of people who customize ITSM 7 to match their needs and if Remedy has identified a bug / defect and they have a fix for it, then they should be able to provide a list of WHAT workflow they are updating / changing. This is frustrating. T. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
