Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
Nope, just reverified it and apparently we have to change the name of the account that is used to login to the computer (very redundant but it’s what the professor required and he deducts points for it).
Thanks for the response!
As far as I know, the "User" column of the file history listing in any particular model file is showing the Username used for your account on whatever network you are using. You can't change this, usually, because it's tied to your credentials for network access, etc.
I don't understand why this would be a problem. Usernames used to access accounts are necessarily unique. Thus, it's easy to use them to verify who is doing things to a particular file. Maybe there's a misunderstanding about what is being required.
Nope, just reverified it and apparently we have to change the name of the account that is used to login to the computer (very redundant but it’s what the professor required and he deducts points for it).
Thanks for the response!
The professor wants to be sure that you actually did the work and did not copy someone else's file. Erasing the file history with that config.pro option would be a flag to me that the file had been copied and was not originally created by the student submitting the project.
The original post asked how to change the name that is in the file history in Creo. For someone working in a business, on a specific domain, the username is not something you can change easily. But, I guess if you are running Creo on your personal PC, you could set up an account with the mandated username on your computer, and only use that login to run Creo.
I'd imagine it's not just "cheating" on assignments, but maybe also getting multiple files with the same name in the file history because people are just using some sort of default?
One would think that if a professor has such a restriction they could perhaps provide simple instructions for the students as to how to comply. It's not realistic to expect people using computers to understand how to do system administration. Or at least not these days.
For those that might find this later:
purge_history_on_save_copy yes
Removes all of the old user names. Its a hidden config. More info here:
