I agree with you Frank -
The bestg thing you can do is "Add to Workspace" and unchecking the "Reuse Content from Target Workspace". It actually gives you flexibility in case if you want to keep your workspace changes.
The definition of the Update action in Windchill differs from Pro/INTRALINK. In Windchill you use the Update action in order to update out-of-date objects, i.e. retrieve a later version of an object to the workspace from commonspace. E.g. you have version 1.4 (A.4) in the workspace and there's a 1.5 (A.5) version in commonspace. The Update action will overwrite the 1.4 version with the 1.5 version. With the dm_overwrite_contents_on_update preference you can set the default behaviour when you have modified the 1.4 version using continue. If it is set to Yes you will overwrite the modification made to the 1.4 version. If it is set to No you will keep your changes but they will have been made to the 1.5 version. E.g if the 1.4 version is a simple extrude. You have modified the 1.4 version using continue, adding a hole.The 1.5 version contains the simple extrude and a round. If you use Update and have the dm_overwrite_contents_on_update preference set to No you would have the 1.5 version in the workspace with the extrude and the hole without the round (i.e. you have overwitten whats in the commonspace). If you check it out and check it in the 1.5 version would be the extrude+hole and not the extrude+round.
The action to overwrite modified content in the workspace (made by you) is Add (read Add to workspace). E.g. you have the 1.4 version in the workspace and you have made modifications to it using continue. You can deselect the Reuse content in target workspace or go to the Advanced tab, select the objects and click Download. I would suggest that you go to the Advanced tab so that you can decide what objects to overwrite and what objects to reuse. E.g. if you use the Add action on an assembly the dependencies set to required will overwrite all modifications made to all parts if you deselect the Reuse content in target workspace check box.
Hope this helps.
Thanks, that's helpful, but still too complicated. Still not sure I follow it actually. Honestly, I think I'll just avoid using the command, and stick to "add to workspace". The Intralink definition is so much better and simpler. You update, and it changes whatever was in your Workspace to be what's in commonspace. Simple, easy to understand. I don't see the need to completely refine terms we were all familiar with to completely reverse what they used to do. Think what would happen if the meaning of stoplight colors was reversed.
Why would someone decide to redefine the meaning of "update" to something else? Update doesn't mean update anymore. What were they thinking? Someday I'm going to meet one of these programmers and maybe we'll be able to come to an understanding. I have never seen a program so unintuitive.