Sharing Between Projects
When you create a new project or program, you are presented with the option Allow sharing to other projects and programs. If you select this option, then parts, documents, and folders can be shared from a project or program to another project. Sharing an object allows members of the target project to reference the object without having access to the rest of your project or program.
For example, if you were a manufacturer collecting quotes, you could share a folder containing a design specification and standard parts from your project to a number of supplier projects. Each supplier project could share a separate quote folder to your original project. This gives each supplier access to the latest version of the design specification without adding the supplier to your project, and ensures that the suppliers are not aware of each other.
Whether you are able to share objects depends on your individual user permissions, the context type, and the Windchill solutions installed at your site.
 |
The ability to exchange information between projects and products or libraries is only available to users with Windchill PDMLink or Arbortext Content Manager installed alongside Windchill ProjectLink. For more information, see Exchanging Data Between Contexts.
|
|
Contexts
|
Sharing allowed?
|
Additional Information
|
|
|---|---|---|---|
|
Source
|
Destination
|
||
Project  |
Project
|
Yes
|
Use the clipboard method described below to share objects from one project to another. For more information, see Sharing from Project to Project.
|
|
Program
|
No
|
—
|
|
|
Product, Library
|
Yes
|
An object created in a project can be sent to a product or library. This object is added to the specified context and then either checked out or shared back to the project. This option is only available to users with Windchill PDMLink installed. For more information, see Sending Objects to PDM.
|
|
Program  |
Project
|
Yes
|
Use the clipboard method described below to share objects from a program to a project.
|
|
Program
|
No
|
—
|
|
|
Product, Library
|
No
|
—
|
|
Product  Library  |
Project
|
Yes
|
There are several ways to share information from a PDM context to a project. For more information, see Actions to Exchange Objects.
|
|
Program
|
No
|
—
|
|
|
Product, Library
|
No
|
—
|
|
When an object is shared between projects, a link to the latest iteration of the source object is created in the target project.
The following rules apply when sharing between projects:
• Only parts, documents, and folders can be shared between projects.
• Objects that have been created in the source project or checked out from PDM to the source project can be shared to another project.
• The Sharing Enabled attribute must be set to Yes for the source project or program.
To modify this attribute, edit the project and set the Allow sharing to other projects and programs option. For more information, see Edit a Project.
• When a folder is shared from one project to another, all folders, documents, and parts in the folder are shared as well. Objects created in the shared source folder are automatically shared to the target projects.
• Access control permissions for shared documents, parts, and folders can be extended to team members and other participants up to the level of permissions granted to the user who is extending permissions to others, provided the user has Change Permissions on the object. An exception is that for parts, the permissions that can be extended are limited to Read, Download, and Change Permissions. For more information, see Setting Access Control on a Shared Object.
• When an object is shared between projects, it is not added to the project baseline. Because the workgroup managers and Creo Elements/Pro 5.0 operate within the context of the project baseline, neither can access objects shared between projects.
|
|
The same permission to share an object between a product or library and a project is required to share an object between projects. For more information, see Permissions and Valid Object Types.
|