Configuring the Revision of Associated Objects
You can configure how Content links are carried forward to new revisions of associated (linked) objects. Using the xconf file, modify <Windchill>/codebase/wt.properties, which contains the following key-value pairing:
Key = wt.vc.struct.copyDescribeLinkOnRevise
Values: No, Yes (default).
With wt.vc.struct.copyDescribeLinkOnRevise set to the default value of Yes, the system behaves as follows for the revision of a dynamic document or part with a Content association.
• There is only one link; iteration-to-iteration.
• If only the dynamic document is revised, the link is not carried forward. The new version of the dynamic document does not have an association to the existing versions of the part (because the existing part version might be released, and the content version of the part should not change without a checkout or revise).
• If only the part is revised, both the new and the old version of the part have a link to the existing version of the dynamic document.
• If both the dynamic document and part are revised during the same revision, the new versions have a new Content link between them, and the old versions maintain their existing link.
When wt.vc.struct.copyDescribeLinkOnRevise is set to No, the system behaves the same as when it is set to Yes, with the following exception:
• If both the dynamic document and part are revised during the same revision, then regardless of the settings in the user interface, revise acts as if the dynamic document and part are being revised alone.