Hi, In addition to RRR|Chive, you might benefit from using RRR|DefHideExpandBox that will help you fix the layout of your forms after the upgrade, as fields 2, 4 and 5 will get an expand box appended to them as a result of a field length increase:
https://www.rrr.se/cgi/tools/main#rrrDefHideExpandBox Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. > Ditto to what Joe said. We moved from 7.1 p7 to 7.6.04 SP2. We simply > just created def files of all of our custom forms and then used RRRCHIVE > to move the data. Something you may want to think about? Then I don't > think you would need to use the interim 7.1 server? Up to you. > > We had about 517 forms to move (plus all the workflow). It really wasn't > that bad.... > > > Thanks! > > Lisa > > > > ________________________________ > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Joe Martin D'Souza > Sent: Tuesday, April 10, 2012 12:25 PM > To: [email protected] > Subject: Re: Transferring in-house 6.3 code to a 7.6.04 server > > ** > If you do not have any OTB applications, I do not think you got too much > to worry about. > > Have you customized any of the core forms? Core workflow? By that I mean > forms like the User, Group, Email Engine forms, etc.. > > If your answer to this is no, you can go your merry way as you might have > in previous versions.. > > If you have customized these core forms and workflow, you might want to > check with BMC if they have a hash file for just the core components, so > that you can create the overlay layer for those customizations. > > And then go your merry way with what you want to do with your in house > stuff.. > > I really do not see much you need to put on your watch list except for > integrations etc you might have done to third party tools or applications > that may face the possibilities of a breakdown if they are not compatible > with the new ARS application server version. > > Joe > > From: David M. Clark<mailto:[email protected]> > Sent: Tuesday, April 10, 2012 12:05 PM > Newsgroups: public.remedy.arsystem.general > To: [email protected]<mailto:[email protected]> > Subject: Transferring in-house 6.3 code to a 7.6.04 server > > ** > Folks, > > I am finally in the process of upgrading our 6.03.00 patch 017 > implementation to the latest offered. By "upgrade" I mean a transfer > between old and new servers, not on the same server. The revs are > apparently too far apart to use Migrator to transfer code between, so I > will be using a 7.1 server as an intermediate transfer point. Migrator > 7.1 from the 6.3 box to the 7.1 box, then the latest Migrator from the 7.1 > box to the 7.6.04 box. I'll also be using Export/Import tools as needed. > Note that no BMC Remedy applications are involved here, though I will be > loading ITSM later. My concern now is only with in-house developed code > created under or compatible with version 6.3. Solaris and Oracle on both > sides. > > Anyone ever done this or have any suggestions as to problems that I may > encounter? > > Thanks, > > -David > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
