When linking two applications, the available OSLC link types depend primarily on the OSLC Resource Type of the linking elements. On this screen, the types of ${term-artifact-type-container-indefinite-singular} can be mapped/unmapped to an OSLC Resource Type. Additionally, linking restrictions/rules can be defined, on ${term-artifact-type-plural}, to be applied when linking from ${local-app} or remote applications.

To visualize or change any ${term-artifact-type-singular} configuration, select first ${term-artifact-type-container-indefinite-singular} from the combo.

Associating an OSLC Resource Type

Locate ${term-artifact-type-definite-singular} to configure in the first column of the table.
Click in the corresponding three-dots icon on the Actions column.
Select the Edit OSLC Resource Type option.
In the opened dialog, select the required OSLC Resource Type minding the warning message.
Click the Update button.

If everything goes well, the dialog will close and the table will be refreshed. Take into account that, as the warning message stated, changing the OSLC Resource Type has several implications for ${term-artifact-type-definite-singular}, and any existing link from/to it may become semantically invalid. Also, take into account that setting None will disable ${term-artifact-type-definite-singular} from any OSLC interaction.

Customizing Linking from ${local-app} Settings

Once ${term-artifact-type-definite-singular} is mapped to an OSLC Resource Type, other than None, it is possible to customize the available link types (when linking from ${local-app}) or whether only the selection dialog, of a remote application, will be available for linking. A default link type can be also set for ${term-artifact-type-definite-singular} in this configuration.

Locate ${term-artifact-type-definite-singular} to configure in the first column of the table.
Click in the corresponding three-dots icon on the Actions column.
Select the Edit Linking Settings option.
In the opened dialog, select the Linking from ${local-app} tab.
Optionally, select the link type, to be preselected in Linking Wizard for this ${term-artifact-type-singular}, by selecting it from the Default Link Type combo. Note: the default link type cannot be disabled, see below.
Optionally, disable an available link type by clicking on the corresponding Disabled radio button. Note: a disabled link type cannot become the default one.
Optionally, disable the linking through the creation dialog of a remote application, for a link type, by clicking on the corresponding Selection dialog only radio button.
Optionally, apply the two previous settings to all link types by clicking in the corresponding Set all radio button.
Click the Update button.

If everything goes well, the dialog will close and the table will be refreshed. The Linking from ${local-app} column will summarize the configuration done by displaying one of the following values:

All link types enabled if both the selection and creation dialogs are enabled for all the available link types.
All link types disabled if both dialogs are disabled for all the link types.
Some link types have restrictions if only some link types, or creation dialogs, are disabled.
Disabled if ${term-artifact-type-definite-singular} was mapped to None.

The Link Types' availability of a Resource Type.

The Link Types displayed for a Resource Type, in Linking from ${local-app} tab, are those corresponding to the OSLC nature of the Resource Type. However, even when they are not disabled on such configuration, they may not be present on Linking Wizard by the time it is open. The reason is those displayed in Linking Wizard also depend on other settings, like the available Project Associations. Do not hesitate to use the Where is my Link Type widget, within Linking Wizard, whenever you don't know why an expected Link Type is missing.

Customizing Linking from Remote Applications Settings

The linking from remote applications can be also customized, for a given ${term-artifact-type-singular}, when the OSLC Resource Type is set to other than None. It is possible to customize whether the remote application can use the ${local-app} creation dialog or only the selection one (and the name of such dialog). An OSLC usage can be also set to help remote applications pre-selecting a ${local-app} ${term-artifact-type-singular} for a given use case.

Locate ${term-artifact-type-definite-singular} to configure in the first column of the table.
Click in the corresponding three-dots icon on the Actions column.
Select the Edit Linking Settings option.
In the opened dialog, select the Linking from Remote Applications tab.
Optionally, disable the remote linking, over this ${term-artifact-type-singular}, by clicking on the Disabled radio button.
Optionally, disable the linking, through the ${local-app} creation dialog, by clicking on the Selection dialog only radio button.
Optionally, rename ${term-artifact-type-definite-singular} to be displayed, in remote applications, as typed in the Dialogs Name field.
Optionally, select the Default OSLC usage, from the Dialogs Usage field, to hint remote applications this is the preferred ${term-artifact-type-singular} to select.
Optionally, check the Prevent changing ${term-artifact-type-definite-singular} inside the dialog checkbox to prevent users from selecting a different ${term-artifact-type-singular} inside the ${local-app} dialog once open.
Click the Update button.

If everything goes well, the dialog will close and the table will be refreshed. The Linking from Remote Applications column will summarize the configuration done by displaying:

Disabled if either ${term-artifact-type-definite-singular} was mapped to None or the remote linking is disabled.
Selection and Creation dialogs or Selection dialog only depending on the selected option.
Labeled as followed by the given Dialog Name if set.
Usage: followed by the given OSLC usage if set.

Note: the adjective exclusive will be displayed along with the available dialogs if the Prevent changing ${term-artifact-type-definite-singular} inside the dialog checkbox was marked.

An initial linking configuration is provided by default to ensure all link types, of all available ${term-artifact-type-plural}, are enabled and no dialog is restricted. On a fresh installation, it is recommended to review this default configuration to make sure it fulfills the company policies.

Link Type	OSLC Usage Picked	Typical Remote Application
Affected by	`Defect`	IBM Engineering Requirements Management DOORS Next
Affected by Change Request	IBM Engineering Test Management
Affected by Defect	IBM Engineering Workflow Management *
Blocked by Change Request	IBM Engineering Test Management
Affected By Plan Item	`Plan Item`	IBM Engineering Workflow Management *
Contributes To
Implemented By	IBM Engineering Requirements Management DOORS Next
Tracks	IBM Engineering Workflow Management *
Tested By	IBM Engineering Test Management
Related Change Request	`Task`	IBM Engineering Test Management
Tracked By	`Requirements Change Request`	IBM Engineering Requirements Management DOORS Next

Validating Linking Configuration

Some validations are performed, on a saved configuration, to ensure the proper behavior of remote applications. If the saved configuration may lead to a weird behavior of remote applications, a warning message will be displayed on the top of the main table. These are the validations performed:

There are unique dialog names (no Dialog Name should be repeated).
No OSLC usage must be repeated per resource type.
No ${local-app} dialog with an OSLC usage set is disabled.

Additionally, info messages are displayed in the following scenarios:

The initial default configuration it is being used (no customizations have been performed).
No ${term-artifact-type-singular} is mapped to an OSLC Resource Type other than None.
If at least one type of type is mapped to a Change Request resource type, all the Change Management usages should be assigned.
If some of the type names match any of the Quality Management resource type names but they are not mapped to them.

Restoring the Default Settings

Once a customized configuration is stored, it is possible to get back to the originally default configuration as follows:

Locate ${term-artifact-type-definite-singular} to restore the configuration in the first column of the table.
Click in the corresponding three-dots icon on the Actions column.
Hover the Restore Default Settings option.
Select whether to apply the option only to the current type or for all of them.
Click Yes in the confirmation dialog.

If everything goes well, the dialog will close and the table will be refreshed displaying the original default configuration for that ${term-artifact-type-singular}.

Unmapping ${term-artifact-type-capitalized-plural}

To remove the OSLC Resource Type association from ${term-artifact-type-plural}, it is convenient to use the unmap shortcut as follows:

Locate ${term-artifact-type-definite-singular} to unmap in the first column of the table.
Click in the corresponding three-dots icon on the Actions column.
Hover the Unmap option.
Select whether to apply the option only to the current type or for all of them.
Click Yes in the confirmation dialog.

If everything goes well, the dialog will close and the table will be refreshed displaying a disabled configuration with no OSLC Resource Type for that ${term-artifact-type-singular}.

Importing mappings

When administering a large number of ${term-artifact-type-container-plural} it can be useful to apply the same configuration to multiple ones. The import mappings action allows to import settings into all applicable ${term-artifact-type-plural} of the currently selected ${term-artifact-type-container-singular} from another ${term-artifact-type-container-singular}.

Click the Import mappings... button above the table.
In the opened dialog, select ${term-artifact-type-container-definite-singular} to import from with the combo.
When loading is finished, a preview of the possible imports is displayed.
Click Import in the confirmation dialog.

The import preview can contain the following feedbacks:

The Type Mappings to import. info message displays ${term-artifact-type-definite-plural} found in both ${term-artifact-type-container-plural} that would be updated.
The Type Mappings identical in... warning message displays ${term-artifact-type-definite-plural} identical in both ${term-artifact-type-container-plural} that would be ignored.
The Type Mappings not found in... warning message displays ${term-artifact-type-definite-plural} missing from the imported ${term-artifact-type-container-singular} that cannot be updated.