Welcome to the #dominoforever Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated jointly by the IBM & HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino page.

Lotusscript events on documents

It would be nice to have onSave and afterSave events on Notesdocuments. Events can be based upon the form used, but should be triggered if saved in backend (and frontend).

This makes it easier to build validation or postprocessing for documents that can be saved both through UI and script.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 19 2018
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 29, 2018 17:08

    I'm curious, we have QuerySave and PostSave / QueryClose already for LS events (Notes client). The "on" events are typically "front-end" for Javascript. We have that too for the Notes Client, although the Notes Client objects need updating of methods and properties, so I tend to use QuerySave w/LS instead. The onSave is typically, the onSubmit for web or Notes development. For web documents, you do have a WebQuerySave event where you can do post were as the document is saving. How are you developing that you don't have them?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 06, 2018 22:04

    Agree. It's a pain to have to replicate QS code in agents/code that is executed in the backend.

  • Admin
    Thomas Hampel commented
    27 Jan 12:07

    Moving to Domino Designer category

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    09 Feb 01:02

    Same - modeChange event.

    I would like to replace the standard behavior of the Client in the above events.