I’ve received questions several times over the past couple of years about adding comments to check out action as well as why can’t we see the check out event in the file history dialog. Obviously, all the check in events show up, some create new version. I’m guessing the two are related?
Is there a setting that would allow adding check out comment and have them show up in file history dialog?
SW2024 has added check out operations to the history and has added the option to check out files as part of a state change.
That’s good to know. Thank you.
But, we’ve been focusing on 2023 as our next version. Trying to get time to set up test PDM servers etc. This seems to be the norm though, get into testing a version & SP then find out there’s a dangling carrot in the next one. Oh well. Good answer never-the-less.
Sorry for digging up an older post here, but do you know a way to turn off history comments for check out and undo check out? Currently running 2025.
I’ve been looking around online and can’t seem to find the right search terms or filter through the noise… It has been ballooning our history, making it hard to briefly see what has actually happened. I admit, I had wished a couple times in the past that I could see when someone checked out a file, but it’s frankly not worth it to us.
Would be welcome but unfortunately no. You can vote (like) here on the enhancement site. There is mention in the post about some client side registry keys that will turn off checkouts and undo checkins for 2025.
Agreed about history view bloat. There are other things (such as automated version free variable updates) that I don’t need to see every time, but don’t mind having the history log. Adding a filter to the history view seems a logical step, IMO it should have been part of the enhancement that was implemented.
Just curious, why are people looking at the history so much? For me it is primarily a troubleshooting thing which isn’t very often.
Sometimes to see who made changes and why, we have a lot of engineers/designer in there doing stuff. And we have a lot of shared components between products. So yeah, I guess you could say its for troubleshooting in a way when models break.
If its ECO related though, we have that documented elsewhere.
What Jason said. As admin I’m looking at file history on multiple files every day, frequently taking screen shots as as the history dialog is a modal.
Users need to be looking at it to understand why other files used in what they’re working on might have been revised or changed state. For the product maintenance group they are all the time revising files that have where used checked out by other people or where used that are part of projects in development. So they need to communicate with the people working on those where used how they want to handle the running changes. Sometimes prototype builds of products in development phase will end up needing a new part as the change makes the production part not compatible with their usage. That’s just a few reasons, I could go on and on. Keep in mind, we needed file management (version history) so bad that we thought it was worth changing CAD systems to get it.
We were on 2023 and honestly I would suggest to test 2025. PDM 2023 administration is full of pitfalls and half broken for us.