Current version in use: Windchill PDMLink 10.1 M020
Current default: Users can add old versions to their workspace. If this older version is not set to a restricted life-cycle state, user may check out non-latest version, modify, and check in.
Note that setting the perference 'Allow checkout of non-latest iterations' to 'Do not allow checkout of non-latest iterations' does not prevent this. This preference simply locks old iterations of each version, without locking old versions.
B.2 - can be checked out and modified
B.1 - cannot be checked out and modified
B.0 - cannot be checked out and modified
A.2 - CAN BE CHECKED OUT AND MODIFIED (This is the problem area.)
A.1 - cannot be checked out and modified
A.0 - cannot be checked out and modified
The problem area described above can have its lifecycle changed to restrict this checkout process. The problem with this as a solution is A) each file is unknown until a user stumbled across it, B) the quantity of legacy files makes searching and then changing burdensome.
The other solution is to make sure users never mistakenly checkout and modify old versions. In other words, make sure users never make a mistake. Might as well try to stop the earth's rotation. With users making this mistake, it ends up having the potential of creating a tremendous problem when modifying CAD docs for change requests or release. The users make modifications to a non-latest version, wasting many hours/days while the admin also has to go in and clean up the problem.
Suggestion: Allow the admin to determine whether to allow older versions to be checked out or not instead of the current behavior of only checking for non-latest iterations.