Here's a thought.I am not entirely sure it will work or not.We used this kind of method when we used PVA's trashcan.That was possible because the trashcan did not have a schema dependency.If recycle bin does not need to be on every server,temporarily configure a server,perform the delete(using lapi,oscript) on that server.If this method works nothing on your prod servers need to change.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
I guess you could create a patch that would override the move to Recycle Bin method and then suspend the DB triggers for Recycle Bin and Notifications so that they are not triggered and then you can do the delete.
Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006
Do you want to physically remove the data, or just remove the refefence to the data? If you want to simply remove the reference - a SQL call might be in order.
If not, and I suspect this is the case, then you will probably have to disable the recycle bin.
One customization I have seen though is to have the document moved into a hidden folder, and the documents from that folder were then able to be deleted with going through the recycle bin - but then, this was a customization and I can't even remember how they did it. This way the company had an out - if they needed to restore a document that had been deleted they could have an administrator pull it out of this hidden folder where he could move it wherever the user needed it to be moved and eveything was auditable - sort of a customized recycle bin with audit trail, if you can imagine this.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.