Include former data in the remove audit entry

[fsalmen-nx]

In a lot of use cases it would be really helpful to include the former data of a removed entity into the audit log. Right now the log only stores that an entity with a specific id was removed. If you for example, use the audit log to audit any user specific data, you might not be able to track for what exactly was deleted.

I would suggest to include the old values in the diff/changeset like it is done in the case of an update.

[DamienHarper]

Hi @RiffFred, sorry for this late reply.
What exactly would you like to have in removal audit entries? It currently contains the id of the removed element and if a __toString() method exists in the relevant entity, it's also evaluated and its result is stored as well.

[fsalmen-nx]

Hi @DamienHarper thank you for the reply.
I thought it might be helpful to include the full audited data of a removed element like it is done in the diff view for changed entities.
Maybe it is just a question of the different rendering between deleted and changed elements.
I think it would be nice to render something like element x was deleted and the element had the following data.
Basically like the diff view for changed elements but with only one site.
For new created elements the audit page also renders the exact data of the element.

If you think that this is not helpful or not doable i will play around with the __toString() implementation thank you for this hint.

[lorenzo-pezzali]

Hi,
also for me this is a good enhancement because i need to have all the fields of the deleted objects not only the __toString result.
Is it possible to implement this with a custom provider or some other way? Or the only method is to change the implementation of the bundle?

Thanks in advance for the response.