Note

The states must be valid life cycle states. The states are defined as key value pairs in StateRb.rbinfo and can be viewed in the life cycle template associated with the object. States are always specified using uppercase characters.

For example, to change the search to include the Released, Approved, and then Completed states of a document, set the preference value to:

RELEASED,APPROVED,COMPLETED

After this preference is set, Windchill searches for the latest Released version first. If none is found, it searches for the latest Approved version. If none is found, it searches for the latest Completed version. So, if a part is linked to Reference Document 4 which has three versions (A, B, and C), where A = Released, B = Approved, and C = In Work, based on the state settings in wt.properties, Windchill displays the latest iteration of version Awhich was released and ignores the rest.

Part to Part Relationships (Projects Only)

A user associates one part with another by using the Structure tab on a part information page. When a user makes the association, a WTPartUsageLink is created, forming a "uses part" relationship between a part and a part master.

The only configuration option for part to part relationships is described in the next section.

Revised or Saved Parent Part to Child Part

When a user revises a parent part using the Revise action or saves the part using the Save As action, the new version of the part carries forward the usage link.

To prevent a link from being copied forward on a Revise or Save As action, you must remove copy rules from wt.properties. For example, assume the following properties are set in wt.properties:

wt.enterprise.copyRuleDelimiter=,

wt.enterprise.copyRulesN=wt.part.WTPart,Relationship,