How can we implement workflow for Deleted content

Question

Hi Experts,
whenever we delete a content , It never went into Workflow.
I want when user delete any content, It should go into workflow. When approver approves it, only then content item should actually deleted. If approver rejects it, content item should not get deleted.
Is there any way to achieve this ??
thanks

Answer 1

Several things jump out about how you may be using delete.
First is that delete rights are set up as separate and distinct from Read and Write (contribute) rights. This is true even for content authors.
There is good reasoning behind this. Basically, because deleting items has special and often regulated meaning, giving users delete permission should be a very intentional action and never a default.
Second, using the "expiry" functionality is a much better and safer option in most cases. Expiring a piece of content removes it from visibility to all except the sysadmin. Expiring content effectively "soft deletes" the item from the user experience while allowing the administrators to still recover the item if necessary. Another advantage of expiring content rather than deleting it is that as the content approaches the expiry date or as an expiry action is triggered, this can automatically trigger actions like a workflow review, email notification, BPEL service call etc. This gives you advance warning as well as the ability to intercept, review, and sign off on the action. You can also run batch jobs to archive and store or archive / delete "expired" items if you determine that you still need to do this.
Finally, if you have considered the above options and still determine that you need to capture "delete requests" then the best option is to write a custom component that intercepts the delete service request and triggers a workflow, notification, expiry or other action.
Remember that when you delete an item you must consider whether or not you are deleting just the latest released revision or all revisions or some selection of revisions. OOTB, UCM allows those with delete permissions to delete revisions one at a time. The repository manager applets provide admins with a bit more batching flexibility.
Hope that helps,
Warmly,
Billy Cripe
Fishbowl Solutions