The short answer: The update functionality has changed. Use "Add to Workspace" from the workspace page for similar results.
Long answer (PDMLink 8):
To achieve the same functionality, go to your workspace, select the part you would like to update and click the "add to workspace" function. In the update window, verify the data you want to update and click next. On this second page, select the parts you want to replace in your workspace and then click the download option. If the part is modified, you will notice a yellow triangle indicating the difference between the workspace version and the version you are adding to the workspace. Click OK to finish the process. If the part is in session, you will be prompted to update it from the workspace.
The above process is a catch-all, there are times when update does work as it did in Intralink, namely when you have not saved your changes AND there is not a newer version in commonspace.
If the file has been modified and saved (but not checked out), and the part has been iterated or revised in commonspace, performing the File--> Update in Pro-E will respond differently based on the settings you have in your environment. This condition is important to be aware of.
The relevant setting is: dm_overwrite_contents_on_update
By default, this option is set to no. If you have not changed this and the above conditions are met, when updating from Pro-E, you will be prompted for an update to your workspace data but not prompted to update session data. (There is a note in the Pro-E message log. See footnotes for the details...) From here, the designer may check out the model without further notification, essentially bypassing the newer geometry. For the designer, this is a bad situation for many reasons, primarily because it is very easy to overwrite changes other people have made without ever seeing them.
By changing the above config setting to yes, when there is a newer version in commonspace, updating your files will prompt you to update even your "changed data". If there isn't a newer version in the system and you HAVE saved changes to your model, you will get the "All the objects in session are up to date." response. Although this is true, it is not consistent with the update experience people appreciated from Intralink...
Best practices from our environment:
- Set dm_overwrite_contents_on_update to yes
- Check out the files you intend to modify
- Use add to workspace to update files
Here is the event message provided when updating modified and saved files when a newer version exists in commonspace:
"Update operation performed on locally modified downloaded objects. Please use "Download" command to bring the corresponding file."