This page is aimed to IBM Engineering Requirements Management DOORS Next 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.

In DOORS Next, all requirements links can be dragged and dropped into the linking wizard, some common cases/places are:

• The Recent Changes widget elements.
• The elements of any Folder content (either the ID or Name columns content).
• The elements of any Collection content (either the ID or Name columns content).
• The elements of any Module content (the ID column content).
• Requirement Links elements.

None of above views support multiple selection for drag and drop, so this must be done one by one. This is true even for Folder, Collection and Modules views where a check box for multiple selection is available; no matter how much of them are selected, only the one from where the dragging started will be dropped.

The multiple selection can be used, however, to perform a multiple paste of URLs: once all desired requirements are checked, right-click on any of them and select the Share Links to N Artifacts... option from the context menu (being N the number of selected requirements); this will open the Share Link dialog containing a text area with all selected requirements' URLs. Select the full content of the text area and copy it to the clipboard, then paste it into the linking wizard.

On a requirement's open page, users can drag and drop the corresponding id number, in the breadcrumbs bar, or the full URL in the browser's addresses bar. They can also open the context menu (right-click) for the id number and select the option to copy the URL of the link. This context menu technique applies also for Links and Recent Changes elements of above list.

Global Configurations Compatibility

DOORS Next projects can work with or without the use of configurations, in technical terms, having Configuration Management enabled or not respectively. Different rules apply depending on this setting:

• When Configuration Management is disabled, no Global Configuration must be locally used in ${local-app} or the linking won't be accepted.
• When Configuration Management is enabled, the rule about Global Configurations 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.

Thanks to the latter rule, the following scenarios are valid:

• When the requirement configuration is a Personal stream (created when working in a Change Set) and it's based on the ${local-app}'s Global Configuration.
• When the requirement configuration is the local configuration referenced by the ${local-app}'s Global Configuration.