The Power of the Configurable Link

A limitation to configurable links, at least master-master configurable links, is that you can only can only have one such link between two objects, even if the link attributes are different.

Hugo, I'm still trying to understand Configurable Relationships...  Re: your comment on Master to Master links... and "you can only have one such link between two objects"  Can you please elaborate?  Are you saying that when setting up Configurable/Master links, I can only have one Master [to WT/Gear] Part relationship?  Or are you saying I can only have one Master-to-Master relationship?    Thanks!

Hi Adam, I don't understand quiet well your hesitation.  Via configurable links, we may add an additional relationship between two WTParts.  Although until now we only have one such a configurable link type set up, I suppose you can set up several such configurable link type.  What we encountered is when you add such a relationship between two WTParts, you can't add a second relationship.  The reason is we added an attribute to the link.  In some cases, we need two links, each link with an own attribute value.

Does this shed a light in the dark?

Does anyone have experience with configuring a "Configurable Described-By Link" in a way, that it has almost the same funtionality as the OOTB Desribed-By link with the exception, that the link is copied forward when the ROLE A Object is revised? So for example:

Part (Released) ---- Document (Released)

Part is revised: OOTB the link to the Document is copied forward. I am looking for an opportunity to remove this link during the revise.