Is there a way to not update the last modified date when only the metadata of a document gets modified, or if I can separate the last modified when contents are modified, and when metadata gets modified?
We have audit seasons every year and the auditors check when the last time a document was modified was. If the documents last modified by date gets updated when only metadata gets changed, this will make them (and us) think the contents of the document were changed.
Thanks
When you do any changes to an object, the version number increases. This is one of the major features of M-Files.
There is nothing you can do to prevent it. It does not matter, if the object itself, or the object metadata changes as that is a modification to it.
Maybe you could have a workflow that prevents any changes after certain state change? The workflow could have a way to return back to a state where you could change the content.
For example, one workflow I've seen looks like the one below, where the article goes through various states until it is "approved" which basically makes it read-only. This is then followed by "published",from where the article can be withdrawn or marked for "update needed" which returns it to draft state, where the content can be changed.
