Greetings - we’ve enabled Document Locking on our databases and have found some issues when attempting to delete documents.
The first issue arose when we went to delete a document. It first states you must lock the document before deleting. Lotus/IBM posted an article that suggests adding @DocLock to the database script > QueryDocumentDelete event.
This works great ONLY IF you’re SURE you want to delete it. However, if you hit delete by accident (as our users often do) and then UNDELETE it, the document remains locked to the user and I (as only a mere designer, not a manager) cannot unlock it.
So, methinks, I got it - I’ll just add @DocLock([Unlock]) to the database script > QueryDocumentUndelete event. Nope - even when I undelete the document, it still remains locked. I tried Field $Writers :=@DeleteField and same on $WRitersDate. No luck. I tried LotusScript. Nothing unlocks it.
My only alternative is to run a nightly agent to ensure everything is unlocked. This isn’t terrible, but it does create an opportunity for Save Conflicts if folks leave a document open overnight.
Any better ideas???
As always, thanks!
Josh
Edited 3:29 EST to explain that I cannot unlock the document if locked to another user.