Design a system to allow to work with the soft-deleted entities

[hikalkan]

My thoughts:

• Create an AspNet Core middleware that disables soft-delete if requested by the client via a cookie or http header. So, we can create a global or page based switch to the UI that sets the cookie/header.
• We should relate this to a permission, surely.

This is very easy way to make the UI working with soft delete entities. But the remaining system should suppose use cases, like undelete an entity. For example;

• Always make the related DTO implementing the ISoftDelete (or inherit from FullAuditedEntityDto or something like that) for the soft-delete entities, so the UI can know if the entity is in the deleted state.
• Add an "undelete" action on the data table for deleted entities.

Actually, anyone can implement it like that for their applications. But we can add this included in the framework level and also implement this for the pre-built modules.

Any other suggestion would be appreciated.

[gdlcf88]

We should relate this to a permission, surely.

Hello @hikalkan, maybe different permissions for different entities, would that be so?

[hikalkan]

Yes thats possible and would be useful

[davidzwa]

Undelete action would make a lot of sense to add to a repository with an interface and base class implementation, although it is pretty simple to implement ourselves.

Currently ISoftDelete is quite lonely without restoration out of the box haha. Is there a thought behind this or just a todo?

[MernaAlbert]

Hello @hikalkan , Is there any new feature added in abp for undelete action for entities who had interface ISoftDelete?