|
Continued from page 3
Some of the following step-by-step processes are referenced in TANs or TPIs at www.ptc.com (numbers are cited where applicable).
Making an instance stand-alone. This process takes an instance out of a family table and makes it an individual object that is no longer related to the family table. Once this is done, you must have “force check in to the same branch” authorization to override conflicts to check the individual object back into the database.
Figure 10.
Example: Company standards state that any parts made from another part must be in the same Pro/ENGINEER family table. Since PartA will no longer be made from PartZ, it should no longer be related to PartZ.
1. Check out generic without parent objects (no upper level assemblies and/or drawings).
2. Open the generic object in a Pro/ENGINEER session linked to the workspace (File, Open) and select generic model name (in the Select Instance dialog, select The generic).
3. Open the instance (from Menu Manager, select Family Table), highlight the instance to be removed from the table, and select the Open button (bottom of the window).
4. Activate generic (from the top menu bar, select Window and select the generic file name from the list).
5. Remove the instance from the table (from Menu Manager, select Family Table; highlight the instance to be removed from the table, select Edit, Delete Rows; confirm deletion.)
6. Verify the family table (select the Verify icon in the family table window, select the Verify button, then the Close button).
7. Close the family table dialog window (select the OK button).
8. Save the generic object (File, Save).
9. Activate the instance (Window; select the instance file name from the pulldown list).
10. Save the instance (File, Save).
11. Respond to storage conflicts message (select the OK button).
12. Prepare for check in as needed. (The instances saved as a stand-alone file are marked as “new” in the workspace and need to have the Commonspace folder location set, along with any usual settings for a new file.)
13. Check in (highlight the new and/or modified objects and select the Check in icon).
14. Override conflicts required. (If the Override button is grayed out, you cannot override the conflict. Notify your local administrator. If the Override button is not grayed out, select it and continue with the check in process.) (Reference TPI 31458 at www.ptc.com.)
Adding a stand-alone object to a table. This process takes an individual or stand-alone object that is not related to a family table and adds it to an existing family table. Once the file is related to the table, you must have “force check in to the same branch” authorization to override conflicts to check the individual object back into the database.
Figure 11.
Example: Company standards state that any parts made from another part must be in the same Pro/ENGINEER family table. Since PartA is now made from PartZ, it must be related to PartZ in a family table.
1. Check out generic to add object to (Find the object in Commonspace, select the Check out option, and follow your standard check out process).
2. Add the instance to the generic (open the family table, insert a new instance and fill in the applicable data).
3. Verify the family table (select the Verify icon in the family table window, select the Verify button, then the Close button).
4. Close the family table dialog window (select the OK button).
5. Save the generic object (File, Save).
6. Prepare for check in as needed. (The instances saved as a stand-alone file are marked as ‘new’ in the workspace will need to have the Commonspace folder location set, along with any usual settings for a new file.)
7. Check in (highlight the new and/or modified objects and select the Check in icon).
8. Override conflicts required. (If the Override button is grayed out, you cannot override the conflict. Notify your local administrator. If the Override button is not grayed out, select it and continue with the check in process.)
Moving an instance to a new table. This process defines removing an instance from a family table and adding it to another existing family table. Once the file is related to the new table, you must have “force check in to the same branch” authorization to override conflicts to check the individual object back into the database.
Figure 12.
Example: Company standards state that any parts made from another part must be in the same Pro/ENGINEER family table. Since PartA is no longer made from PartZ and will now be made from PartX, it needs to be related to the PartX family table.
1. Check out old generic and instances to a Workspace (Find the object in Commonspace, select the Check out option, and follow your standard check out process).
2. Remove the instance from the table (from Menu Manager, select Family Table; highlight the instance to be removed from the table and select Edit, Delete Rows; confirm deletion).
3. Verify the family table (select the Verify icon in the family table window, select the Verify button, then the Close button).
4. Close the family table dialog window (select the OK button).
5. Save the generic object (File, Save).
6. Check out the new generic to the same Workspace (Find the object in Commonspace, select the Check out option, and follow your standard check out process).
7. Open the generic in Pro/ENGINEER (File, Open).
8. Add the instance to the new generic (open the family table, insert a new instance and fill in the applicable data).
9. Verify the new instance (select the Verify icon in the family table window, select the Verify button, then the Close button).
10. Save the generic object (File, Save).
11. Prepare for check in as needed. (The instances saved as a stand-alone file are marked as “new” in the workspace and need to have the Commonspace folder location set, along with any usual settings for a new file.)
12. Check in (highlight the new and/or modified objects and select the Check in icon).
13. Override conflicts required. (If the Override button is grayed out, you cannot override the conflict. Notify your local administrator. If the Override button is not grayed out, select it and continue with the check in process.) (Reference TPI 32308 at www.ptc.com.)
|
