All, During a call today I was asked how long it would take to apply this patch to a 7.0.0 patch 2 system (running Incident, SLM and Requestor). So would any one care to guess from start to roll out on production on that time frame? This would include testing.
Howard On Nov 7, 2007 12:12 PM, Carey Matthew Black <[EMAIL PROTECTED]> wrote: > Also... please do not forget the fact that ITSM is also about data > configuration too. The objects that are changes are only one part of > the puzzle of "what a patch does". > > It is a difficult enough of a task for us to figure this stuff out by > brute force. However there are several RFE's that should make it easy > enough for _all of us_ (mostly BMC) to "get along" with everyone else. > > To name a short few: > > ) Like the Server Event's per object during an Import of a def/XML > file. (instead of just one server event for the whole object import > operation) > ) Like using data auditing on core/ITSM configuration forms. :) > ) Like having a real way to validate the install after it is complete. > And not just look at the last data record that should have been > created/updated. But a validity test for every element(object/data) > that is involved in the product/patch. > > -- > Carey Matthew Black > Remedy Skilled Professional (RSP) > ARS = Action Request System(Remedy) > > Love, then teach > Solution = People + Process + Tools > Fast, Accurate, Cheap.... Pick two. > > > > On Nov 7, 2007 10:52 AM, Michiel Beijen <[EMAIL PROTECTED]> wrote: > > Well yes, you can find the ardisable utility on the old Remedy > > Community and it is also in the new BMC Developers Network > > (http://www.bmcdn.ws) > > Of course it would be appropriate for Remedy to include a list of > > touched workflow with the release... but since there is no such list > > currently the best way to go is - imo - using the scenario I described > > earlier. > > If anyone has a better idea of how to install an ITSM patch; please let me > > know. > > > > Regards, > > > > Michiel > > <snip> > > > > > 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" > -- Howard Richter ITIL Foundation Certified Red Hat Certified Technician CompTIA Linux+ Certified [EMAIL PROTECTED] Resume = http://hotjobs.yahoo.com/resumes/hrichter_1/resumeofhoward _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
