Can "Overwrite latest version" be set as default so users don't have to select this option each time checking in a file?
Can "Overwrite latest version" be set as default so users don't have to select this option each time checking in a file?
Like "working copy" in workgroup PDM, it's not my intent to use it every time checking in file.
will check off this option for each major change
it's my habit to keep checking files into Vault (just in case SW crashing" and I don't want to keep many file's versions in the Vault
I see your reasoning now. While I understand that as a CAD user, as a PDM Admin it still makes me uneasy.
I'm not sure of a way to set that option by default. I would assume that it's not able to be done but I don't have a version of PDM with that feature to check.
Saving would accomplish this, no need to check in just for crashes.
Some users here keep checking out big assembly and checking back in the Vault with no change on it
I thought with the option as default, we would avoid adding versions
Then the question is why are they checking them out in the 1st place?
Edit: also, "undo check out" if for exactly that purpose.
there are all kinds of "excuse" and I don't want to deal with it so I thought it'd better to set this option default
Sorry to say, and you probably already know this, but it sounds like you are treating the symptom instead of the cause.
Indeed, I try to get vaccine for the cause
Am I missing something? It sounds like you are misunderstanding versions and revisions.
Versions are just a sequential number tracking what has changed from one to another. I always "cheap" & constantly tell the users to check-in a file as often as they feel they need to (although I'd question the reasoning if somebody were checking in their files more than say twice a day) and to simply just keep it checked out if you are still working on it. I really don't care that it bumps the file version, that has nothing to do with the revision.
I've also set up workflows (for the users coming off of Workgroup) to add a "+" to the end of the revision when a file is transitioned from Released to WIP. It's a visual reminder to the user that the rev is not at a "released" state.
Tom Cote wrote:
Am I missing something? It sounds like you are misunderstanding versions and revisions.
Versions are just a sequential number tracking what has changed from one to another. I always "cheap" & constantly tell the users to check-in a file as often as they feel they need to (although I'd question the reasoning if somebody were checking in their files more than say twice a day) and to simply just keep it checked out if you are still working on it. I really don't care that it bumps the file version, that has nothing to do with the revision.
I've also set up workflows (for the users coming off of Workgroup) to add a "+" to the end of the revision when a file is transitioned from Released to WIP. It's a visual reminder to the user that the rev is not at a "released" state.
Thank you for your concern but I understand exactly the differences between Version vs Revision
Sorry for confusing as I'm not asking about revision here - in our workflow, file is only changed Revision at the final released state and it's locked
I also tell the users to check in files more often in the pre-released states but not to add a new version for each minor change by using "overwrite latest version" option. However, users kept forgetting to use this option so I want (if possible) to set it as default
Overwrite latest version every time will destroy any version history you have for a part. If for any reason you have to roll the part back to a previous version and somebody overwrote it when they made the change then there is no way to recover from that from what I understand.
This feature exists to make very minor corrections such as a mis-spelling in a custom property or to hide a sketch so it doesn't automatically show in upper level assemblies.