When a new version is stored but no changes have been made to the document, the stored version replaces the last stored version or audit log associated with the state of the document. This might cause behaviour that users may not expect.
Let's say user A created a document and has stored a version when A was finished editing.
Then user B comes along and wants to make some edits, but before B does, creates a version to be sure to save the current state. If there were no edits in-between the new version created will effectively replace the version created by A which will then disappear from the list. While both versions point at the same state of the document, to users it might be surprising that creating a new version makes another version disappear.
The same applies to the last auditlog entry created before a version is saved.
It would be more intuitive to always store a new version when this is requested in the UI, regardless of whether it already existed.
When a new version is stored but no changes have been made to the document, the stored version replaces the last stored version or audit log associated with the state of the document. This might cause behaviour that users may not expect.
Let's say user A created a document and has stored a version when A was finished editing.
Then user B comes along and wants to make some edits, but before B does, creates a version to be sure to save the current state. If there were no edits in-between the new version created will effectively replace the version created by A which will then disappear from the list. While both versions point at the same state of the document, to users it might be surprising that creating a new version makes another version disappear. The same applies to the last auditlog entry created before a version is saved.
It would be more intuitive to always store a new version when this is requested in the UI, regardless of whether it already existed.