Data Management Capabilities > Exchanging Data Between Contexts > Interoperability and CAD Integration > Shared Objects in Workspaces
Shared Objects in Workspaces
All workgroup managers, including Creo Elements/Pro 5.0, are linked to a workspace. When a workspace is created, it is associated to a context. The context can be a project, product, library, or the entire PDM system. For more information, see Introduction to the Workspace.
A workspace can be linked to the system or a context in Windchill PDMLink. In this case, you can search, download, and modify objects that are contained in any of these contexts. When a workspace is linked to a specific project, you can search, download, and modify only those objects contained in the project. You cannot perform these actions on objects contained in other projects, products, or libraries.
All CAD integrations operate by using the project baseline and project configuration specification. The project sharing filter identifies the set of shared object iterations that are considered whenever you download objects or update your workspace. By default, this is the latest iteration.
Because the workspace always uses the project configuration specification, the following options are not available when setting the latest configuration specification in the collector:
Specify life cycle state.
Use latest configuration for unresolved dependents.
The sharing filter configuration is used for shared objects.
A workspace can point to iterations and versions of parts and CAD documents that are not specified by the project baseline or sharing filter. This might occur after you update a project. You can later update the workspaces to include updated objects in the project baseline.
The following example illustrates how a project might behave when you bring a new iteration of a shared PDM object into your workspace:
1. Part A.1 is shared to the project from PDM. A share link to the PDM object is created in the project folder, and Part A.1 is added to the project baseline.
2. User A downloads Part A.1 from the project to their workspace.
3. From the PDM context, User B then creates a new iteration (Part A.2) of the object in PDM. The project baseline and the various workspaces continue to point to Part A.1.
4. Later, the project is updated to pick up new iterations of the shared object. In this case, Part A.2 would replace Part A.1 in the project baseline. After updating the project, all downloads of the object to a workspace include Part A.2 rather than Part A.1.
5. When User A is ready to move up to Part A.2 of the shared object, they can use the Update action in their workspace browser.