Your Development & Design Resource

VIDEO: NotesDocument Auto-Save Teaser

While I'm still playing around with the demo of my NotesDocument Auto-Save engine - which I'm developing specifically for an article in the IBM Lotus Domino Designer Wiki - I thought that I would at least show an in-progress teaser demo.

The idea here is simple: The Auto-Save runs - in this example, every 5 seconds - and saves the UI Form's contents to a temp NotesDocument via HTTP POST over AJAX. For the initial submission - which creates a new temp NotesDocument - said NotesDocument UniversalID is returned and put into a field (which I would typically set to hidden). All subsequent auto-saves use that UNID value as the POST target.

When/if you finally submit, you're actually editing the temp NotesDocument and submitting it to the NotesDatabase as a document.

The idea here is that workflow and application logic may be tied to the document, so we keep it a temp NotesDocument until it's submitted. A simple clean-up Agent can be setup to purge any temp NotesDocuments that were not submitted... and you now have your simple-yet-fully-functional NotesDocument Auto-Save engine!

FYI: All NotesDocument reads and writes are done via the Domino CRUD API!

About the author: Chris Toohey

Thought Leadership, Web & Mobile Application Development, Solutions Integration, Technical Writing & Mentoring

A published developer and webmaster of, Chris Toohey specializes in platform application development, solutions integration, and evangelism of platform capabilities and best practices.

More from is powered by IBM Notes Domino XPages & hosted by Prominic.NET

Contact Us

Use our Contact / Feedback form or one of these email addresses:

Creative Commons License

Except where otherwise noted, by Chris Toohey is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.