Dependent Objects Included in Replication Disowning
To collect dependent objects during the replication disowning process, specific roles must be selected based on the type of replicated link. Some links require a designated role to initiate the discovery, while others allow either role to be used as the starting point. The system collects the entire version history of the selected replicated object (also known as the seed object), along with its replicated dependents.
The table below outlines the required role for each type of replicated link to ensure proper collection of associated replicated objects.
* 
Access checks for the Replication Authority and Replication Package Administrators groups are applied when displaying objects in reports, but not during the actual collection of dependents. Administrators must define policy access rules for the Replication Authority group. For more information, see Best Practices for Disowning by Replication Process.
Dependency collection rules are predefined and maintained by PTC. Only PTC can modify these rules.
Link
Selected Role
Collected Role
wt.epm.build.EPMBuildRule
EPMDocument or Part
Part or EPMDocument, respectively
wt.change2.ReportedAgainst
Problem Report
Problem Report and Part (affected object)
wt.change2.AffectedActivityData
Change Task
Change Task and Part (affected object)
wt.change2.ChangeRecord2
Change Task
Change Task and Part (affected object)
wt.change2.RelevantRequestData2
Change Request
Change Request and Part (affected object)
wt.change2.SubjectProduct
Part Master (affected end item)
Part Master (affected end item) and Change Request
wt.Change2.ProblemProduct
Part Master (affected end item)
Part Master (affected end item) and Problem Report
wt.epm.structure.EPMVariantLink
Family Table Generic or Family Table Instances
Family Table Instances or Family Table Generic, respectively
ChangeReferenceLink
Flexible Change Item
Flexible Change Item
FlexibleChangeLinkDependencyProcessor
Change Request or Change Notice
Change Notice or Change Request, respectively
wt.change2.HangingChangeLink
Change Task
Change Task and Part (resulting object)
wt.change2.RelevantAnalysisData
Analysis Activity
Analysis Activity and Part (affected object)
wt.change2.SupportingDataFor
Change Object
Supporting Material and Change Object
wt.change2.FormalizedBy
Problem Report or Change Request
Change Request or Problem Report, respectively
wt.change2.ResearchedBy
Change Object or Change Analysis
Change Analysis or Change Object, respectively
wt.change2.AcceptedStrategy
Change Notice or Change Proposal
Change Proposal or Change Notice, respectively
wt.change2.AddressedBy2
Change Notice Change Request
Change Request or Change Notice, respectively
wt.change2.DetailedBy
Change Analysis or Analysis Activity
Analysis Activity or Change Analysis, respectively
Various Effectivities
Any Effectivity- Managed Object (example: Part, Document)
Any Effectivity
wt.change2.ChangeProcessLink
Flexible Change Item
Flexible Change Item
wt.epm.build.EPMBuildHistory
EPMDocument or Part
Part or EPMDocument, respectively
wt.epm.structure.EPMDescribeLink
EPMDocument or Part
Part or EPMDocument, respectively
wt.epm.build.EPMBuildRuleAssociationLink
EPMDocument or Part
Part or EPMDocument, respectively
wt.epm.modelitems.ModelItemContainedIn
EPMDocument
Model Item
wt.epm.structure.EPMContainedIn
EPM Document or EPM Family Table Objects
EPM Family Table Objects or EPM Document respectively
wt.change2.IncludedIn2
Change Notice
Change Notice and Change Task
If a selected replicated object includes a link type not listed in the table above, only the object itself will be collected for disowning; its replicated dependents will not be included. As a result, such dependents will not appear in the Summary_Dependency_Chain or Summary_Objects_ToBe_Disowned reports. However, the replicated link will still be converted into a local link.
For more information on these reports, see Replication Disowning Summary Reports.
Was this helpful?