Basic Administration > Managing Data > Project and Program Administration > Understanding Projects and Programs > Configuring Part and Document Relationships (Projects and Programs) > Part to Document Relationships (Projects) > Document Version Used with Reference Link (Projects and Programs)
  
Document Version Used with Reference Link (Projects and Programs)
As described earlier, Part Reference Link links (WTPartReferenceLink) link to a document master, but display a document version of the master based on the life cycle state rules for the document.
The default behavior is that Windchill searches for the latest released version of the document to display. If no version of the document has been released, it displays the latest working version of the document.
To change the default behavior, change the value set for the List of comma separated life cycle states of documents used to display associated Reference documents to part. preference in the Preference Management utility.
* 
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 A which was released and ignores the rest.