Does N2O Checkout/Checkin support concurrent development?
N2O Checkout/Checkin supports up to 15 levels of concurrent development. In concurrent development situations, N2O provides a warning message when the program is selected for migration. Each checkout user is then aware that other users are working with the same program. This enables users to coordinate their changes to ensure the integrity of the production environment. Question: Our site has a “Librarian” who performs all of the migrations at our site. If we use N2O Checkout/Checkin, it looks as though the Librarian will have to transfer the checkout of each migrated program to the programmer before the programmer may begin modifying it, and transfer it back before migrating the program to the next environment. Can we configure N2O so that our Librarian is still responsible for all program migrations, but avoid all of these checkout transfers? Answer: Yes. There are two ways to accomplish this. One of the simplest is to configure your environment so that all migrations require “author
