Link Constraints feature not working for Custom created link types across PA in DNG 6.0.2 version
2 answers
It really depends on how you configure the Link Constraints. If you specify an artifact type for both the source artifact and the target artifact, the specified link type will be limited to the current project area only. If you need the rule to apply across project areas, either the source or the target has to be ANY. The document actually clearly states this.
http://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.2/com.ibm.rational.rrm.help.doc/topics/c_link_constraints.html
One critical concept that you need to understand is that, artifact types with the same name in different project areas are actually _different_ types. For example, "Feature" in project A is not the same as "Feature" in project B. This implies that, you cannot set a link constraint such that a specific artifact type can only link to another specific artifact type in the other project, at least for now.
A second thing to note is that while ANY allows cross-project links, it also allows linking to _any_ artifact types within the same project area.
And lastly, less restrictive rules override restrictive rules. For example, if there are three rules - "Feature > Child Of > ANY", "Feature > Parent Of > ANY" and "Feature > Child Of > Feature", then the last one has no effect.
http://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.2/com.ibm.rational.rrm.help.doc/topics/c_link_constraints.html
One critical concept that you need to understand is that, artifact types with the same name in different project areas are actually _different_ types. For example, "Feature" in project A is not the same as "Feature" in project B. This implies that, you cannot set a link constraint such that a specific artifact type can only link to another specific artifact type in the other project, at least for now.
A second thing to note is that while ANY allows cross-project links, it also allows linking to _any_ artifact types within the same project area.
And lastly, less restrictive rules override restrictive rules. For example, if there are three rules - "Feature > Child Of > ANY", "Feature > Parent Of > ANY" and "Feature > Child Of > Feature", then the last one has no effect.
Comments
Thanks for the information. As you said cross project linking works fine for system defined link types (if link constraints are set to “Any”), but if I create my own custom link type and use the link constraint in the same way as used for system defined link types, it does not work.
So here my question is more specific to Custom Link types, not system defined link types.Have you came across this scenario?. Thanks!
