Does N2O make it possible to load a revision into a production application, but not use that revision until a later time, when the old version has been backed up and the new version activated?
Yes. There are a number of ways you might accomplish this with N2O. One of these ways is the postdated migration. By postdating a migration to occur at a specific time, the site can postpone when the revision will be loaded into the production environment and activated. With archiving enabled for that application library, N2O will automatically backup the old version of the application before moving the revision into the library. The new version can then be automatically compiled and will become the active version. The N2O developers can discuss other alternatives provided by N2O. Question: When a new version of an application is in production and is not performing as intended, can N2O back it out of production so that the application returns to the way it was before the revision was applied? Answer: Yes. By doing a “restore” from the N2O archive, it will be possible to back out the changes you have made and restore the application to its former status. The revised application will be
Related Questions
- Does N2O make it possible to load a revision into a production application, but not use that revision until a later time, when the old version has been backed up and the new version activated?
- If I submitted a paper application on time, but found out later that some pages are missing, may I submit the missing pages before the 30 day-before-review deadline?
- Is it possible to save the analysis conditions with the spectrum so it can be quantified correctly at a later time?
