This guide section is aimed for OSLC Remote Application users. It assumes the reader is familiar with general use of the application.

Creating Links

The process to create OSLC Links can vary from one OSLC Remote Application to another. However, differences are only on how to start such process because once you reach the selection or creation dialog, the behavior within these dialogs is the same. Here is the process to start the selection/creation dialog:

  1. Select the artifact you want to link.
  2. Look up for the links section and select the option to add a new one.
  3. On the adding dialog or page, select one of the available link types [1]
  4. In the target container field, look up and select the associated ${local-app} ${term-project-singular} [2].
  5. Complete the authentication process, if a pop-up window appears [3], to log-in ${local-app} and approve the connection.
  6. Select the option you want to use for linking:

Removing Links

Once the OSLC Link is created, the process to remove it is the same as for other kind of links:

  1. In links section, approach the mouse over the link to remove; the OSLC Remote Application must provide a way to remove the link, it could be a delete icon or a contextual menu with such an option.
  2. Click or select the option provided by the OSLC Remote Application to remove the link.
  3. If a confirmation dialog is displayed, confirm your decision to remove such link.

If everything went as planned, the dialog will be closed, the link will be removed from the system and it will no longer appear in the links section. If, on the other hand, you see any kind of error message, please contact your administrator in order to check the license validity of ${local-app-connector}, or any other issue before continuing. At this point, the safest is to cancel the process and wait for a resolution.

Viewing Links

Each OSLC Remote Application provides a mean to display the linked artifacts and to show the rich preview of the linked artifact when the mouse hovers it, a request which ${local-app-connector} fulfills.