#dominoforever | Product Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! 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 by 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
Welcome to the #dominoforever Product Ideas Forum! 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 by 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
Check out http://blog.nashcom.de/nashcomblog.nsf/dx/nshdellog-domino-deletion-log-annoatation-and-backup.htm
If you have been following what has happened after V10 is launched, you would know that:
Since the initial request only mention logging deletion to a database those two combination should be adequate, right ?
It should be added to the deletion stub as additional fields
It was announced, to be logged in a text file. I prefer it to be optionally logged in the deletion stub.
I think the requestor is suggesting it be enabled on specific databases, not every database on the server.
You could always enable soft deletions and then run an agnt on a view showing these documents during off peak hours to record deletion time / person responsible and server / document particulars to a log before removing them permanently.
Wouldn't this level of logging be resource intensive? I've seen Activity.nsf kill busy servers.
I think has already been announced as an upcoming feature!