Locking and Unlocking Objects in the Workspace

Integration with Other Applications > Windchill Workgroup Manager Documentation > NX > PDM Actions in NX > Locking and Unlocking Objects in the Workspace

Locking a workspace object gives it a read-only status in the workspace and in the NX session. The action is only available from an active workspace.

You may want to make an object read-only for any of the following reasons:

• To avoid inadvertent modification.

• To reduce the number of times that the Conflicts window is presented for objects that are not intended to be modified.

• To give the user better visibility into changes made implicitly by NX (for example, unplanned or unexpected changes required during regeneration/rebuilding) .

• To prevent the object from being saved.

Read-only object status is a property of the local cache, whether the workspace is online, offline, or portable. There is no notion of a locked object in the server-side workspace (which is viewed in standalone browser) or the commonspace.

The preference Workspace > Add to Workspace and Checkout > Automatically lock objects added to workspace can set the workspace lock default to automatically lock all objects that are not being checked out during Add to Workspace and Checkout operations.

The CAD worker ignores the Automatically lock objects added to workspace preference and successfully publishes the CAD documents, which are locked.