This page is aimed to IBM Engineering Requirements Management DOORS Family users to let them know which elements can be dragged/copied and dropped/pasted into the ${local-app-connector} linking wizard, as well as some limitations the application has using it.

DOORS Family client users can drag requirements directly from a Module and drop them into the linking wizard. Alternatively, they can right-click on any of them and select the Copy URL option to paste it using Ctrl + V.

DOORS Family Web Access (DWA) users does not have the option to drag and drop, they can only copy and paste the requirements URLs through:

1. In an opened Module view, select the requirement to link by clicking on it.
2. Expand the System tab in the Attributes panel on the right.
3. Lookup for the URL attribute and right-click on the link.
4. From the context menu, select the option to copy the link.
5. Back on ${local-app}, paste the clipboard content in the linking wizard.

Out of the box, it is not possible to drag and drop more than one requirement at once, no matter if it is possible to select more than one: only the one from where the dragging started is going to be dropped on the linking wizard, this is due to a limitation of the DOORS Family client itself. Fortunately, ${local-app-connector} comes with a DOORS Family add-in to workaround this, ask the DOORS Family administrator to install it, and once done, a new OSLC Connect menu will appear on the opened Module window. Then:

1. Select the first requirement of the set by clicking on it.
2. Select the last requirement of the set by clicking on it while pressing the shift key.
3. Open the OSLC Connect menu and select the option Copy Selected Object Urls.
4. Back on ${local-app}, paste the clipboard content to process all copied URLs in the linking wizard.

Global Configurations Compatibility

Up to version 9.7.1, there is no difference between using a Global Configuration locally in ${local-app} or not, the same elements discussed above are suitable to be drag-and-dropped or copy-and-pasted in the linking wizard. This is due to the nature of the DOORS Family application and because it does not support Configuration Management at all.

Starting 9.7.2 version, DOORS Family modules can work in the context of a Global Configuration, and when they do, the fourth validation about GCs, mentioned in the parent topic, applies: if the dropped/pasted requirement does not exist in the configuration used by ${local-app}, the linking is not accepted.

The elements from where the dragging can start are the same; however, it is worth mentioning that only the current version URL is carried for dropping. In other words, no matter if you were dragging a baseline requirement, you will end up with the current version requirement once dropped. The workaround to this situation is to use the copy/paste approach; this way, the versioned requirement URL is used and then you can create unidirectional links from ${local-app} to baselines requirements (links cannot be bidirectional because it is not possible to modify the baseline requirement to add the backlink to ${local-app}). Do not forget that the Global Configuration locally used in ${local-app} must match the one used by the baseline in this case.