Windchill 10.2 and File Update in Pro/E

[qnen]

We are getting ready to go live with Windchill 10.2 and Pro/E Wildfire 5.0.
We are currently using Windchill 9.1.
In 9.1, when I open a part in Pro/E (not checked out, just open), the state of the part is shown in the title bar. If I go to the server (vault), change the state of the part, and then come back to Pro, I can do a File Update Current and the Pro/E session reports the new state in the title bar. (workspace is obviously updated as well)
In 10.2, I am not able to do this. After changing the state on the server, I have to go to the current workspace window and do a Tools Synchronize to get the Pro/E session to show the new state in the title bar. Seems like a loss of functionality.

Am I missing a setting or preference somewhere?

Michael Kuehnen, Kansas City

 

[looslib]

What build of Creo/Elements Pro are you running? PTC says you need to be at M200 or higher.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[qnen]

Wildfire 5.0 M220

Michael Kuehnen, Kansas City

 

[looslib]

Reading your description of the steps required, I don't see much difference, other than where you do the update.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[qnen]

The desire is to keep the steps the same. We have some users on the manufacturing side who interact with Pro/E in a very minimal way. Open Pro, file open part, export as step, get out. We have taught them that the File-Update will guarantee that they have the latest and greatest version. Now, they will need to perform an extra step. (Doable, but not ideal).

The perfect solution will be to script their pro/e startup to empty workspace first. It's on the to do list along with lots of other customizations.

I have an open ticket with PTC to see if we can get the update behaviour in 10.2 to be similar to 9.1.


Michael Kuehnen, Kansas City

 

[looslib]

If manufacturing is only using the files to do an export, I would teach them to always empty the workspace when done, so if they ever need a file it will ALWAYS be the latest pulled from the server. No update, no resync, just the latest file.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[qnen]

Finally found a setting under the Workgroup Manager Client -> Update Overwrite Local Content. I think this is what I was after. Having this set to yes seems to cause a File->Update in Pro/E to update the workspace AND the proe session with any changes made in the main vault.

Michael Kuehnen, Kansas City