When an entry is renamed in the repository Audit Trail 11 is reporting the Event Type as "Move Entry". Is there a reason it doesn't report it as "Rename Entry" instead? It makes it harder to narrow down those events.
Though I'm not sure why, it is documented behavior:
Move Entry: Tracks when a document, folder, or shortcut is moved. It also tracks when an entry is renamed.
There is no separate "Rename Entry" audit event.
I've since learned more about this and gotten the answer. From a backend perspective, by changing the entry name you're moving it to a new full logical path. That you're moving the entry to a new file location (\CurrentFolder\NewName) rather than a new folder (\NewFolder\CurrentName) doesn't matter - it's still a path move operation.
As @████████told me: "That is, a resource only has a path and from some perspectives a shouldn't matter how close the before and after paths are, it's a move. It's one of those cases where the UX doesn't really match the thinking in the backend, and it gets exposed to the user."
That makes sense on the backend. Is it something that could be updated in the future, so it reports it in Audit Trail as a rename instead if just the last part of the new full logical path has changed?