WTParts–Change Notice Linking Approach

[MS_11082662]

I'm exploring configurable links for change management. Can you walk me through your approach to linking WTParts with Change Notices, especially:
- how the custom link type was defined,
- how you automated link creation when parts are added to Affected Objects, and
- how you exposed these links so users can see which products have running changes?
Any implementation tips would be very helpful.

Reference topic: Solved: What is the use of configurable links in windchill... - PTC Community 

[joe_morton]

Hi,

I'm curious why you're investigating configurable links. Why not use the out-of-the-box links? If I'm not mistaken, WTParts can link to a Change Notice as either Affected Objects or Resultant Objects. 

[MS_11082662]

Currently i am exploring the Collective configurable link.  tha the is aviable in the ptc help center. I had doubt on it,   

Hello,

Thank you for taking over this case. I would like to give you a quick overview of the issue so we can continue smoothly.

We are facing a problem with the Configurable Link Collection features in a vanilla Windchill environment (no custom code involved). In the Save As UI and the  and in the Configurable Link Collector, the following default Windchill actions are not working as expected:

• Collect related Describe child objects

• Collect related Master child objects

  

• Collect related Reference child objects

• Collect related Revision child objects

• Collect related Describe parent objects

• Collect related Master parent objects

• Collect related Reference parent objects

• Collect related Revision parent objects

These icons/actions are part of standard Windchill functionality, but they are not behaving correctly. 

[joe_morton]

I want to make sure there's no misunderstanding - you posted your question to the PTC Community page. This isn't a place for PTC Support cases, it's a place where community members help each other with questions and such.