Integration with Other Applications > Windchill Workgroup Manager Documentation > NX > PDM Actions in NX > Update for NX
Update for NX
If CAD documents are iterated on the Windchill server, then your Workspace copies becomes out-of-date. You can use the Update command to update the object information in your Workspace with the information available in your Windchill server. You must also use the update command after applying specification changes to your Workspace. Update aligns the version of objects available in session with your primary Workspace in accordance with the Workspace configuration specification. The Update command is always unidirectional, and begins from the server to replace what is in session in the Workspace.
For example, a Workspace configuration specification is Latest, and A.2 version of an object is added to your Workspace. In the meantime, a different user has checked out this object and checked in an A.3 (latest) version to the Workspace. (A Workspace preference allows you to set the defaults used for this action.)
To update an object in NX, click Windchill > Update Active Model or Windchill > Update All Models. In Windchill Workgroup Manager client, select the object, and then click File > Update, or click the update icon on the workspace Object List table toolbar.
* 
If the Out Of Date and Out Of Date With Workspace Configuration columns are displayed in the Workspace, during each Workspace refresh, Windchill checks the Workspace for objects that are out-of-date with respect to the Workspace configuration specification. A notification appears when an object is out-of-date. These columns are not displayed by default, as a check during each refresh slows the Workspace refresh.
When replacing out-of-date components in an assembly that is already open in session, you no longer have to close and reopen the assembly to complete the Update action. Assembly components in the Local Workspace can be replaced with updated ones while the assembly is open and in work. In NX, when a Family Table is modified, the entire assembly will be closed and updated.
* 
In NX, assume an assembly is open in User Session A, and an assembly/child of a parent assembly is added or replaced by another user, who then updates the parent assembly in User Session A , then the new child added will not appear as loaded in the NX feature tree as well as in the graphics area. The second user must select the check box in the feature tree for that CAD Document to be seen in the graphics area. This is a known limitation of NX.
Was this helpful?