4. After the object(s) are checked in, import the second-oldest version of the same Pro/ENGINEER object(s). When the object(s) are imported over the existing file(s), Pro/INTRALINK treats the imported object(s) as a new object version. The Workspace Status appears as Modified, the version number remains at 0 until checked-in, and the folder location is retained from the previous check-in.

Fig. 6. Import window and directory structure of second object(s) being imported (click figure to view entire image).

Fig. 7. Second version of imported object(s) in Workspace (click figure to view entire image).

Note: A conflict may appear stating that a part with the same name already exists in your Workspace. Click OK to override the conflicts.

5. Add the attribute information and modify the revision if necessary.

Fig. 8. Object(s) in Workspace after changes have been made, with revision set to "A" (click figure to view entire image).

6. Check in the modified object(s) into the Commonspace.

7. Click the Baseline tab within the Checkin window, and create a baseline for this version.

After these object(s) are checked in, repeat the preceding steps until the version history for all object(s) has been imported.

Fig. 9. Import Dialog window and directory structure of third object(s) being imported (click figure to view entire image).

Fig. 10. Third version of imported object(s) in Workspace (click figure to view entire image).

Fig. 11. Latest version of object(s) in the Commonspace (click figure to view entire image).

Fig. 12. Baseline information of checked-in object(s) (click figure to view entire image).

Fig. 13. PIV Info of checked-in object(s) (click figure to view entire image).

To import assemblies:

Importing assemblies follows a similar process, given that the assembly version has a parallel history as the components. This is, however, seldom the case. To overcome this, you must:

1. Import the part objects into the Commonspace and then the assembly objects. Keep in mind that an older version of the assembly would not use the latest versions of the checked-in part(s).

2. Map out a timeline of when the objects (assemblies and parts) were created and then import these objects to create the complete version history as mentioned in the previous steps.

This will be a tedious process, but it is essential if you want to maintain an assembly's complete history.

Keith Ebling is a design engineer/consultant working through M.J.
Consultants, Inc. at Baldwin Hardware Corporation in Reading, Pennsylvania, USA. He can be reached by e-mail at ebling@baldwinhq.com.