Idea Delivered Partially

Starting from Tridion Docs 15.1 IDelete plugins are supported on Content Objects (Document objects like topics, maps, libraries, images, and others), Publication Outputs, Publications and Publication versions, and Baselines

Delete plugins similar to Write plugins

Proposed interface:

Current access model allows read or write access only on the folders. Child folders get the same access similar to the parent folder. In this way, we do not have the complete control on the child folder's objects like graphics or topics. If we have the Delete plugins with the help of metadata on the items, delete action can be controlled more precisely. 

Muralikrishna Prodduturi
Parents

  • In the initial design of the .NET based plugin system, it was deliberately chosen to name the plugins "IWrite..." indicating that they would trigger on write operations like create/update/checkin/etc. By extension there are entries on our backlog for "IDelete..." and "IMove...", the other typical verbs you want to track. The last verb is "IRead..." but offering plugins here might completely slow down any system (definitely if the implementation is poor on performance).

    So in short, we are aware, it however never made it to the top of the backlog.

Comment

  • In the initial design of the .NET based plugin system, it was deliberately chosen to name the plugins "IWrite..." indicating that they would trigger on write operations like create/update/checkin/etc. By extension there are entries on our backlog for "IDelete..." and "IMove...", the other typical verbs you want to track. The last verb is "IRead..." but offering plugins here might completely slow down any system (definitely if the implementation is poor on performance).

    So in short, we are aware, it however never made it to the top of the backlog.

Children