Actually the Windows user is used to create or use the Windchill Cache Directory.
If different Windchill users log in under the same windows login, the cache can be corrupted.
When the cache is created after the windchill login and with the information from this login, a Windchill-Cache-Sub-Dir is used for the session.
then it is possible to log in with different Windchill users (Library-Admin, Designer, Approver)
If this wold be combined with an Logoff/Logon functionality in Creo or Windchill...
With this change we and our customer will save a lot ot time and misunderstanding!
We already realized this as a workaround in our Creo start tool. Changing the Windchill user there is creating a different Cache folder and changes the PTC_WF_ROOT system variable to this folder. This would not be necessary anymore if the cache would not be mixed up when differnt user try to connect Windchill.
For our Creo/Windchill Admins we have a couple startups that point to different cache folder locations using PTC_WF_ROOT. Each one has a separate icon. Eventually I may get around to making a better UI for it.
If I had to test another account I've had to rename the cache folder, do the testing, and then rename the folder back.
It would be beneficial if it isolated the cache by user, that would eliminate the corruption issues it already warns about when swapping out Windchill users on the same cache.
I would think it's pretty standard across IT that if you have different roles you should have different accounts with varying levels of power. You shouldn't be doing design work with a Site Admin account as you could unintentionally edit things. Testing requires changing caches even more to go through different roles.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.