Disabling Auto save in DNG module

mohan kumar (78●9●30) | asked Feb 23 '17, 4:28 a.m.
edited Feb 23 '17, 4:30 a.m.

Hi All,

Is it possible to disable auto save in DNG module. where after adding /changing artifact in a module and click outside the artifact will save by default. as shown in the below snapshot.

autosave

Regards,
Mohan

One answer

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Donald Nong (14.5k●4●14) | answered Feb 23 '17, 4:38 a.m.

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

mohan kumar commented Feb 23 '17, 7:14 a.m. | edited Feb 23 '17, 7:15 a.m.

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.

Nate Decker commented Feb 23 '17, 12:20 p.m.

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.

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

It's all about the answers!

Related questions

Disabling Auto save in DNG module

One answer

Your answer