Generic and Family Table instances should be in Same version/Revision

[AS_11081239]

Version: Windchill 12.1

Use Case: Creating family table instance for existing solidworks generic sldprt. existing Generic have revision B.1, Family table created with Revision A.1

Description:

Hi Community,
want to maintain the Revision for Generic and Family table instances with same revision,
Here one of user take generic Cad part of solidworks which existed in C.1 version and user created family table instance for that CAD Part and checked in new family table was created as A.1 version.
this there is mismatch of parent generic CAD and Family table instance here. So we wanted to maintain same version of generic CAD part in family table instance CAD part.
Is it possible in Windchill? this need any customization? or any preference management OOTB options available?
please help.

[avillanueva]

This is certainly not OOTB nor is there a preference to control this. This would your organizations business rule and should be handled via a change process or release process. There are a number of preferences for collectors (like Revise collector) that you should use if you want to make it less mistake proof to avoid not including instances on revise for example. Your rule is not a bad one and I think one that most companies follow. Its just that not all will so its not forced upon all users that its the only way to managed them.

You can customize a listener to fix the revision on instances to match the generic when creating them later. You also have the option before checking to bump a newly created instance of an EPMDocument to a higher revision but not once its been fully checked in.

[BenLoosli]

By default all new objects are created at version A.1. This can be changed through OIR rules are manually. 

This is one reason why I do not revise family table parts, even when adding new instances. All of our family table parts are at revision A. These parts are also controlled by being in a Library and only the system admins have librarian privileges to edit them.

Depending on how many you have it may be just as easy to revise the ones that are not at the same revision as the generic to that revision.

[DmitryC]

There is a setting in Windchill Preference Management that defines the initial revision from SolidWorks custom properties:

On top of that, we have a custom new configuration macro in Solidworks that creates new configurations with an option to define the revision (it just creates the appropriate custom property):

We also have a custom SolidWorks Add-in. One of the things that this add-in does - it deletes this custom property when the new instance is created in Windchill (so things won't get messed up if you do a save-as).