If users delete requests, they are gone and it not logged who deleted them. In general, it is not advisable to allow users to delete anything from the system (cancel should be enough). You could of course create an audit trigger and table, that logs deletions.
As a trigger is a backend operation that will be tricky, you cannot use tokens there. The first thing that came to my mind was the last_updated_by column, but that probably will not be updated before the deletion. You need the person who last opended the request before deletion. A rule could populate a field in the request with that person, but again this will not be saved to the DB unless the user clicks on save. My idea would be the following: - a functin in the DB that saves the user_id in an unused user_data field for that reuqest - a rule that triggers on page load with an SQL like select myFunction([SYS.USER_ID] from dual - one more (hidden) text field in the request to store the result of the function to - the audit trigger that uses the stored user_id as the person who deleted the request
We don't have such auditing (deleting is not allowed for anybody except an admin), we just audit changes to references (including removed/changed attachments). hth