Doesn't 7.1 migrator keep a copy of the original workflow prior to it being modified? Maybe migratory has some fall back capabilities.. But as patchsk said, usually you document every detail in your change ticket. and test, test, test.. so you won't have to back out. :)
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of patchsk Sent: Thursday, June 02, 2011 4:51 PM To: arslist@ARSLIST.ORG Subject: Re: How to rollback the changes once we depolyed on the server? There is no easy automatic way. Incase of a mass release db restore is an ideal option. But for small and medium releases it is not an ideal option. Usually you create a change ticket per feature. And document the workflow being touched on each change ticket and attach the backup instructions with the code. You can refer that during the rollback. If you really need to automate then you end up creating custom scripts, I do not think not many people do that. On Jun 2, 1:25 am, Vikram_Betholi <betholi.vik...@gmail.com> wrote: > Hi, > > We are moving our code to production server using migrator scripts.If at > some point of time we want to revert back particular functionality, how can > this be done automatically? > > With Regards, > B.Vikram. > > ___________________________________________________________________________ > ____ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug11www.wwrug.comARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
