That's a conundrum that we all have to ponder, Mary. I wish I had a better answer, but here's my $0.02. We generally have to make the changes as we find them, since BMC is months behind on bug fixes, and we don't know how long it might be before they fix what we're finding for them.
Sorry you had to be the one on the bleeding edge for patch 5, but since you are, do you have a list of the forms and workflow object changes contained therein? I asked for same and was met with the digital equivalent of a blank stare - they apparently hadn't thought that someone might actually be interested in knowing what they're putting on their system before they put it there. They did bug the patch process, but declined to provide the information. (sigh) Rick -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 18, 2007 8:17 PM To: arslist@ARSLIST.ORG Subject: Should we be fixing vendor bugs? Hi AR Listers, I'm not sure if this question has been posted before. We are on IM/PM 7.0.2 patch 5 and have found some out of the box bugs from our system testing. Some of these bugs are high priority for us to fix them now because they cause either confusion to users or inconsistency. We've reported some in the past but not sure whether they would be fixed in the next patch. Our concern is that if we fix them by ourselves would it cause add-on complexity when we apply the next IM/PM patch (in case they do get fixed in the patch)? How do you handle vendor bugs if they are something you have to fix sooner than later? Your feedback is much appreciated. Thanks, ~Mary 949-975-5180 ext - 55180 ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
