Link constraints in the RM application

Link constraints are rules that an administrator can set up to specify which kinds of links are allowed in a project or across projects. If no rules are created, all links are allowed. However, if you create rules, only the links in the rules are allowed.

Administrators can create link rules on the Link Constraints tab in the project properties. These rules govern the creation of links in Requirements Management (RM) projects and across RM projects on the same server.

Note: Link constraints cannot span applications.

Link creation with link constraints

After you create link rules, the options for creating links from context menus and in the Create Link window are affected by those rules.

In the following example, a single rule specifies that a Business Goal artifact has a Satisfies link to a Vision artifact:

New Rule window

Because this is the only rule in the project, no other links are allowed. If you are creating a link from a Vision artifact or Business Goal artifact, only the Satisfies and Satisfied By link types are available. No other link types are available from any other artifacts.

For example, if you create a link from a Business Goal artifact, only the Satisfies link type appears as a menu option:

Menu option for Add a Link to the Artifact

In addition, in the Create Link window, you can select only those artifact types that are allowed based on the initial artifact type and the selected link type, as shown in the following image:

Create Link window

Tip: Link rules constrain only new links that are created. Links that existed before you created or changed the rules are not affected by the new rules. However, you can search for and manually modify links that don't adhere to any new or changed constraints; for example, if the link type is no longer allowed, but the artifact types do satisfy the constraints, then you can change the link type. If, however, the artifact type is not allowed, then you can only delete the link type.

To enable linking between artifacts in different projects, you must define a rule that allows linking for the particular link type in both projects, and the rules must match. When you create cross-project links, rather than using ANY as the link end, you can select a specific artifact type in target project.

For example, for the "Link (Link To/Link From)" link type, if you want Business Goal artifacts in Project 1 to link to Feature artifacts in Project 2 (which also implies that Feature artifacts in Project 2 can link from Business Goals in Project 1), you must define the rules as follows:

Project 1:

Business Goal artifact links to any artifact type

Project 2:

Any artifact type links from a Feature artifact

These rules match because both directions of the link type are allowed in each project.
Note: If a project does not have any constraints, it is compatible with all rules. For example, suppose Project 1 has a rule that a Feature artifact can link to any artifact type. If Project 2 does not have any constraints that are defined, the Feature artifact in Project 1 can link to any artifact in Project 2. However, if Project 2 has constraints that are defined, an explicit matching rule must exist in Project 2.

When you create link constraints, you can also select a cross-project or cross-component type as a link end. The cross-project or cross-component name is displayed after the artifact type name. For example, you can create a constraint such as Business Goal (Project A) Link To Vision (Project B), where Business Goal is the source artifact type, (Project A) is the source cross project type, Link To is the link type, Vision is the target artifact type, and (Project B) is the target cross project type.

Note: If you add a link constraint for a remote project, and that project is enabled for configuration management, you must be working in a global configuration.

Flexibility for link rules

You can make link rules more flexible by using ANY as the target artifact type. For example, if you create a "Link" link type for a Business Process Diagram artifact, and you specify ANY as the target artifact type, you can create links from a Business Process Diagram artifact to any artifact type in the current project.

Link Rules window

In addition, you can specify ANY in a link rule to enable links to web resources or to artifacts in another RM project.

Automatic generation of link constraints

As a project administrator, you can automatically generate link constraint rules validate the existing link relationships by clicking Generate Rules. The link constraint rules that are required to satisfy existing link relationships are identified and appended to the list. If your project includes cross-project links, the cross-project rules are also automatically created for the specify project. To create the corresponding rule, you must click Generate Rules in the linked project.

You cannot automatically generate link constraints for custom types. If you create two projects that each have their own custom type, and create a link between them, when you click Generate Rules, the rules are created by using the ANY keyword. For example, the first project would contain a Project1CustomType Link to ANY rule, and the second project would contain a ANY Link To Project2CustomType rule.

Preferred link types

Preferred link types that you specify for an artifact type are subject to the link rules that are in effect. For example, if you have a preferred link type of Satisfies for an artifact type, but your link rules do not allow this link type, the Satisfies link type is ignored.

Versioning constraints

Constraints are versioned and handled by the configuration management capabilities; they can vary across configurations, be delivered in change sets, and can be compared and merged.


video icon Watch videos

CLM playlist
Jazz.net channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions

Jazz.net forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog