Uploading Objects from Workspace Cache
Use the Upload action to store working copies of the files you are editing in your registered CAD application. The file is uploaded to your personal folder location on the Windchill server (your server-side workspace), without visibility to other users. The Upload action puts local changes into the server-side workspace, but not into the commonspace. (A checkin is required to make new objects or changes to objects available in the commonspace).
|
|
Care should be taken in using the workspace’s Remove objects from workspace action, as it removes objects from both the client-side and server-side workspace views.
|
Upload is valid for new or modified files. Supported files include those in the following states.
• Files that are not checked out
• New objects with a duplicate filename with objects already in the commonspace or in another workspace.
|
|
Creo Parametric and Windchill Workgroup Manager can be configured so that files saved to the client workspace are also uploaded to the server workspace. This ensures that the information is available on the server. There are additional advantages to configuring this behavior, as well as file management and performance considerations, due to the need to avoid conflicts at checkin. For more information, see the section, Considerations when Using Upload on Save to Workspace.
|
|
|
• In Creo Parametric, set the config.pro option dm_upload_objects to ‘automatic’ to upload objects upon > . The default value is ‘explicit.’
• In Windchill Workgroup Manager, set the wgmclient.ini preference save_to_ws.upload to ‘Yes’ to specify the default setting for the Upload option in the Tools menu of the Save to Workspace or Save to Windchill window. ‘Yes’ is the default setting.
• Selecting a workspace object for upload also selects its new or modified dependent objects to be uploaded.
• You can have system-generated CAD document names and/or numbers assigned without a file extension by setting the following server-side preferences to Yes. The default is No (generated numbers and names include the file extension).
◦ > > >
◦ > > >
|
To upload objects:
1. In the active workspace, select the objects you want to upload and select > or click the upload icon
.
The
Upload page appears, displaying your initially selected objects and any new or modified required dependents in the
Object List table.
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. You can collect objects for the upload action using the advanced mode of the collection user interface, which includes options to set a configuration specification. The basic collection mode is not available for this action. For more information, see
Collecting in Advanced Mode.
| For the upload action collection, only the add drawings control (  ) is available. However, selecting the advanced collection icon  also allows you to specify in the Advanced Add window to collect Source or Image objects related to the selected object. |
3. Clicking the set location icon
(also available in the
Location column) presents the
Set Location window to allow you to select the
Context and storage
Location for the selected object. See
Setting a Location.
4. If enabled at your site, the Organization ID field allows you to enter the identification number of an organization. Alternatively, click Search to open the Search Organization window to search for an organization or its ID.
5. You can reset the
Object List to its original state by clicking the reset icon
.
6. If the objects selected for upload or objects added to the list based on dependencies include incomplete dependent objects (see Incomplete Objects), the Auto resolve incomplete objects check box is also available. When selected, the auto-resolve functionality offers the following two options.
◦ Update with object on server, then ignore—The system searches on the server for an object with the same file name. If one is found, the incomplete object is updated by the found file. The object is no longer incomplete, and is therefore available for upload.
If no object is found to update the incomplete object, the system ignores the incomplete dependent (which is removed from the upload list).
◦ Always ignore—The system simply removes any incomplete objects from the upload list.
| Site administrative settings may not allow the ignore option. Required dependents cannot be ignored. |
7. Click OK.
After a successful upload, the workspace symbol for modified content status is removed.
Considerations when Using Upload on Save to Workspace
When all local content is uploaded to the server, the following advantages are provided.
• Consistent standalone and embedded workspace views.
• Allows Workspace Save As for modified, non-checked-out objects.
• Allows upload of CAD documents with filenames that duplicate filenames of CAD documents existing in the commonspace or in another workspace Filename uniqueness is still enforced by check-in failure of an object with duplicate filename.
| Filenames must be unique within the same workspace, even if the object with a duplicate name is unseen. An example is when a family table member is added to a workspace. The names of other members of that family table are checked by the system for naming conflicts. This is true, even though those other instances do not appear in the workspace listing. |
• Provides users with ability to move between different machines without compromising workspace data.
• Provides workspace backup on the server.
With workspace upload, you should be aware of the following points.
• CAD objects having filename or numbering conflicts with objects already in the database or in another workspace display that status in a column called
Conflict Information. This status column does not appear by default, but can be added to your workspace table view.
For more information on customizing your table view, see Customizing Table Views. • A CAD object’s number must be unique at checkin. If autonumbering is enabled at your site, no issues should arise. However, at sites where users can edit number, and specify number to be the same as filename during a Rename operation, a number conflict is possible. To support the upload of objects with duplicate filenames, having a duplicate number, a preference has been created. If the preference, > > > , is set to yes, an object with a numbering conflict is assigned a temporary number in the workspace. You have to edit this temporary number to a unique number before being able to check the object in.
| This preference should only be enabled when system configuration allows editing of the number field during Rename. |
• When you try to upload objects from workspace cache with attribute constraint violation or type mismatch, the upload operation completes with a warning. However, to check-in those objects to commonspace, you must resolve the type mismatch or constraint violations. Else, the check-in operation fails.
