Edit transaction tracking: Log all edits, including deletes, in a separate table (no-code)

[Bud]

It would be helpful if there were OOTB functionality in Pro that would track all edits in a separate table (including tracking deleted rows).

For example, a rough idea might be:

(would need further consideration / open to ideas)

• Not the same thing as editor tracking fields (only tracks creation date/editor and last editor/date; doesn't track deletes).
• We don't want to use archiving. We don't want to store all edits in the master table. That makes things messy when it comes to SQL queries...we don't want to deal with the clutter of having old edit info in the master table.
• We're aware that this kind of thing can be done using attribute rules or with custom database functionality. But we don't want to write custom code for this. It would be better if we could use OOTB functionality.
  • This seems like a common requirement. Lots of people seem to write attribute rules for this kind of thing...to track transactions in a separate table. Ideally, we wouldn't all be writing the same custom functionality. Could it be offered OOTB instead?