Published markups are carried forward to every new version of a file, and there is no way to turn this off.
For an example, after a review we automatically copy files that achieve status A or B to a Published folder, to comply with ISO standards. However, when that same status B file (with comments) is resubmitted (from shared) and should now be awarded an A (no comments), we have an issue with old comments rolling over within the published folder. The reviewer manually deletes comments during the review from the file in shared (however he can only delete his own), and once the file is clean it's stamped status A and copied into Published again. However over there, old comments from the previous version are brought forward, when they should be removed like in the Shared folder. Here, we end up with a status A drawing (no comments allowed) with comments (rolled over form previous status B version). Members are not allowed to tamper with files in the published location (ie. the purpose of the published status), so our only option is for our administrator to go in an delete old comments, which is not scalable, reliable or without risk of manual errors. we also end up with inconsistent information across the files, when they are supposed to be identical.
What we need:
A project (or folder) level setting ensuring markups apply only to the version they were created on, the same way stamps currently work. When the setting is on, older markups are still visible on previous versions, but not automatically copied over.
Without this function we are unable to use the folder structure ISO 19650 requires (WIP/Shared/Published).
