Disabling Auto save in DNG module
One answer
I doubt it. What do you expect to do if it is not saved automatically? Edit another requirement at the same time? Navigate to somewhere else without remembering whether you have manually saved the previous changes or not?
Comments
hi Donald,
Thanks for the quick response,
We are trying to avoid the accidental changes to a artifact while navigating through module.
If we have a save button inside module. we might get a notification that this artifact has been changed do you want to save it of not.
I would note that this is how the desktop client for the DOORS classic application worked. All changes were made cached locally and only committed when the module as a whole was saved. This had great performance advantages versus the RDNG implementation of performing HTTP communication with the server after every action, but it did run the risk of losing a lot of uncommitted changes. Being a desktop client, that didn't typically happen. It would probably be harder to implement this in a web-based application, but the performance benefits could still be worth it.