Adding Objects to the Workspace
Use the Add command to update workspace objects, or to add objects from the commonspace to your workspace. The files associated with the objects can optionally be downloaded to your local disk so they can be opened in your CAD tools. In the Windchill Preference Management utility, you can set preferences for Add to Workspace and Check Out behavior. For more information about the preferences, see the related topics at the end.
* 
You need "Download" access permission to add objects to the workspace and open them in CAD tool.
CAD application dependency rules and the status of workspace objects affect which objects are ultimately selectable or de-selectable for download. In addition, you may be able to download some objects, check out others, or check out only meta-data for yet other objects. (Windchill PDMLink orWindchill ProjectLink only)
To add an object to your workspace, do the following:
1. Navigate to the object in the commonspace (for example, an object's information page, search results table, or a folders page), then select the object. Next, select Add to Workspace from an object's Actions menu or right-click actions menu.
The Add to Workspace page appears. By default, the page displays the basic mode of the collection user interface.
On the Basic tab, you can specify your criteria for adding the object and any related objects to the workspace. Optionally, you can toggle to the advanced mode of collection by selecting the Advanced tab. In the advanced mode, you can use table features to personalize your view of the listed objects. For more information on basic table use, sorting, using and customizing views, and finding strings in the table listing, see Using Tables and Customizing Table Views.
2. If you are initiating the add to workspace action from the commonspace, you can select a target workspace in the Workspace field. You can also create a new target workspace by clicking New.
3. Use the collection user interface (basic or advanced mode) to specify the objects to add, remove, include or exclude from the object list. the interface includes options to set a configuration specification.
4. If you are adding the object to an active workspace (connected to local cache), you can specify how you would like primary content handled, using one of the following methods:
In the basic mode, select one of the following rules from the Primary Content menu. This applies to all the objects collected for checkout.
Download—Content is downloaded to workspace upon execution of action.
Link—Only metadata is downloaded to the workspace and a link is created to the commonspace content for later content download, if necessary.
* 
To reuse the contents available in the local cache, check Reuse modified workspace content option. This option is applicable only to the objects whose iteration in the workspace matches the iteration in the Add to Workspace user interface.
If user initiates add to workspace for object or objects that are modified but not checked-out, then the download option adds the Original Copy or Checked in version to the workspace.
The default is to reuse the content in the local cache.
In the advanced mode, specify primary content handling by selecting objects and applying the appropriate action. You can use either the Edit menu or the table toolbar. The current content-handling setting for each object is indicated by a symbol in the Workspace content status column. The following table describes the content-handling controls and indicators:
Edit Menu Selection
Toolbar Icon
Indicator Symbol
Description
Download Content
Content is downloaded to workspace upon execution of action.
Add Content as Link
Only metadata is downloaded to the workspace and a link is created to the commonspace content for later content download, if necessary.
Reuse
No content is downloaded. Instead, the content on the version currently in the target workspace is used.
* 
This option is applicable only to the objects whose iteration in the workspace matches the iteration in the Check Out / Add to Workspace user interface.
The versions of related objects collected in the Advanced UI can be configured using the Edit Filter controls on the toolbar. For more information about setting configuration specifications in the Edit Filter, see About Configuration Specifications.
5. Set objects to be checked out, as follows:
If you are working in the Basic mode, set a rule by selecting one of the following types of objects from the Checkout drop-down menu. The rule applies to all objects collected.
None—No objects are checked out.
Initially selected and modified—Only the initially selected objects and modified dependents are checked out (available only when the target workspace is an active workspace).
Initially selected—Only the initially selected objects are checked out.
Required—Initially selected objects and any required dependents are checked out.
All—Initially selected objects and all dependents are checked out.
If you are working on the Advanced tab, select table objects and then select File > Set for Check Out or click the checkout icon in the table toolbar. A checkout symbol appears in the Action status column, indicating your intent. (Clicking the checkout icon a second time toggles off the selection).
6. Optionally, to remove your specifications for object collection and handling, and return the table to its original state, click the reset icon (in advanced mode only).
7. If your target workspace is an active workspace, you can select the Open initially selected object(s) in Authoring Application check box. This action automatically opens each initially selected object in an individual CAD session window upon execution of the add action.
8. Click OK. The selected objects are added to the target workspace as you have specified. By default, the objects are not locked in the workspace and can be modified in the CAD tool.
Handling Conflicts
Consider a scenario where you are viewing an object that has multiple versions. If the version you are viewing differs from the version in the workspace, attempts to add the objects may fail due to an overridable conflict related to family table instance incompatibility. You can resolve this conflict by completely replacing the existing family table members in the workspace with compatible members from the current instance.
Isto foi útil?