Description | |
---|---|
Artifacts |
Double-click text artifacts and diagram artifacts to edit them You can now double-click in the content area of a text artifact or diagram artifact to put it into edit mode. |
Go to a specific page of artifact results When you view a list of artifacts on the All, Collections, or Modules tabs, a page navigator is shown at the bottom if the list spans multiple pages. If there are six or more pages, the page navigator includes an ellipsis. You can now click the ellipsis, which opens a Go To Page dialog box. In the dialog box, you can specify a specific page to navigate to. Image of the Go To Page dialog box: |
|
Improved rich-text editing Tables You can now select several cells in a table, which means you can perform these actions:
Font name and font size The Font Name and Font Size drop-down menus now show values that the editor does not directly support. For example, if you copy and paste text from Microsoft Word in a font that is not on the Font Name menu, the font is displayed as a read-only item on the menu. If rich text does not have a font name or font size explicitly specified, the Font Name and Font Size menus show the default font name and font size. Image of the Font Name menu: Paste actions The Paste dialog box was removed. When you select the Paste or Paste as Plain Text menu options, a message instructs you to use the Ctrl+V or Ctrl+Shift+V actions to paste. Image of the paste message: |
|
Open Artifact option opens new modules or collections in view mode When you create a new module or collection and select the Open Artifact option, the module no longer opens in edit mode. When you create a new module or collection, the Open Artifact option opens the newly created module or collection in view mode. |
|
Support for Greek capital letters The Insert Symbol dialog box now includes the symbols for Greek capital letters. Image of the Insert Symbol dialog box: |
|
Type counts on the summary page of the rich-text extraction wizard now reflect the results in the destination The summary page of the rich-text extraction wizard now shows a count for the number of occurrences of each type in the Artifact Type column in the destination (a module or folder). In previous releases, a different counting method meant that the sum of the types did not always add up to the total count in the Artifacts row, and the count was the same for importing to a module or a folder. Now, the counts on the summary page vary depending on whether you save to a module or a folder. The different counts occur because of the differences between modules and folders. If you save to a module, the artifact count summary matches what you count if you open the module and count all instances in the Artifact Type column. If you save the results to an empty folder, the same relationship is shown between the grid in the folder and the artifact summary page. The Artifacts row in the import summary is the sum of all the artifact types below it. The Comments and Images rows are a total count of the number of images and comments in the source (and which should also be in the destination). |
|
When you extract requirements from existing text artifacts, embedded text artifacts are now reused by default In previous versions of Rational DOORS Next Generation, embedded text was not always reused when text was extracted from existing artifacts. Instead, depending on the product version and whether you saved to a folder or module, the embedded text was saved into new requirements. Now, the original embedded artifacts are always reused to prevent duplication and to save space.To revert to the original behavior, you can change the advanced administrative property named "Reuse embeds during text extraction" to false. |
|
Links |
Create Link dialog box shows the project associated with each component When you use the Create Link dialog box, the Component drop-down menu now shows the project associated with each component. Image of the Create Link dialog box with two C1 components: one in the Test1 project and the other in the Test2 project: |
Module or folder selections persist in the OSLC link dialog box When you create OSLC links, the link dialog box stores the last selected module or folder. The setting persists across sessions. |
|
See the target for cross-project or cross-component links in the Create Matching Trace Link dialog box The Create Matching Trace Link dialog box now indicates the project or component for cross-project or cross-component links. Image of the Create Matching Trace Link dialog box: |
|
Type-ahead search for projects and components was improved in the Create Link dialog box In the Create Link dialog box, when you start typing to look for a project or component, the search mechanism looks for matches anywhere in the project or component name. Image of the search results after typing to look for a project: |
|
MBeans |
Obtain server information by using MBeans In this release, Rational DOORS Next Generation offers several MBeans (specifically MXBeans) that provide information about the internal status of the running server and its data. For details, see RM MBeans Descriptions. |
Merges |
Direction arrows clarify deliveries in the merge wizard In the merge wizard, an arrow shows the direction of each delivery. Different arrows indicate "deliver all from source," "keep all from target," and "merge." Image of the merge wizard with a direction arrow: |
The source and target are clarified in the merge wizard In the merge wizard, both configurations are now tagged as source and target. The former "Proposed" label was changed to "Proposed for Target" to clarify its purpose. Image of improved merge wizard: |
|
Modules |
Child artifacts are identified when you remove artifacts from modules When you remove artifacts from a module, the child artifacts that will be removed are identified and a dialog box confirms that the child artifacts will be removed. Image of the confirmation dialog box when you remove artifacts from a module: |
Identify when a module is sorted When the contents of a module are sorted, a Clear Sorting button is shown on the banner toolbar. Click the button to remove the sorting and the button. Image of a module sorted by ID with the Clear Sorting button on the banner toolbar: |
|
In modules, the menu items to show hierarchy levels now act immediately In modules, when you use the Configure Page Settings drop-down menu to select how many hierarchy levels to show, a check mark is no longer displayed beside the menu selection. Now, when you select these menu items, only rows with a depth at or below the selected level are shown. In previous releases, the results would change only when you selected a different menu item. Now, you can select the same menu item again to change the results. Image of the menu item to show hierarchy levels: |
|
Message is displayed when a drag-and-drop operation fails in a module that is sorted or filtered Previously, when you attempted to drag and drop items in a module with a sort column or at least one filter, the operation failed. This behavior was confusing because there was no indication of why the drag attempt failed. This behavior has changed. You can now drag and drop the items, but a warning at the top of the page indicates why the drop failed. Image of dragging and dropping in a module that has a sort column or a filter: |
|
When you open a module for the first time, the Selected Artifact tab is shown The first time that you open a module, the Selected Artifact tab is now shown. Previously, the Module tab was shown. However, the tab that you select is preserved across browser sessions, so if you change to the Module tab, the next time you open that module, the Module tab is selected. The text on the Selected Artifact tab changed and more prominently indicates that you must select an artifact to see any content. Image of the Selected Artifact tab in the right sidebar of a module: |
|
Reports |
Settings are stored when you create a report from a module When you generate a report from a module, the "Create a Report" dialog box stores your most recent settings. These settings persist across sessions. |
ReqIF |
Import information is available for uploaded packages When you use the Advanced option to import requirements from a ReqIF file, detailed information for each uploaded .reqif file is available. You can see how many specifications, artifacts, types, and attributes are in the uploaded package. Image of import information after a ReqIF package is uploaded to the server: Similar information is shown when you import a ReqIF package that is already uploaded to the current project or component. |
Prevent modifications to artifact types and data types during an advanced import When you use the Advanced option to import requirements from a ReqIF file, you can prevent modifications to artifact types by clearing the Allow modification of existing artifact types check box in the Advanced Import Options window. This option prevents changes to the title, description, and RDF URI of all artifact types. Similarly, clearing the Allow modification of existing data types check box prevents changes to the title, description, and RDF URI of all data types. |
|
Public API for ReqIF definitions Rational DOORS Next Generation now provides support for managing ReqIF definitions through an API. Applications can use the API for these tasks:
For details, see Rational DOORS Next Generation ReqIF API 1.0. |
|
Receive error reports for specific package errors For advanced ReqIF imports, the analysis report now shows information on these types of errors if they occur in an incoming ReqIF package:
|
|
Restrict modifications to attribute definitions during an advanced import When you use the Advanced option to import requirements from a ReqIF file, you can prevent modifications to attribute definitions by clearing the Allow modification of existing attribute definitions check box in the Advanced Import Options window. This option prevents changes to the title, description, and RDF URI of all attribute definitions. |
|
Restrict moving artifacts in modules during an advanced import When you use the Advanced option to import requirements from a ReqIF file, you can prevent artifacts in modules from being moved by clearing the Allow artifact move check box in the Advanced Import Options window. This option prevents artifacts in modules from being moved during the import. |
|
Restrict the creation of artifacts during an advanced import When you use the Advanced option to import requirements from a ReqIF file, you can restrict the creation of artifacts by clearing the Allow artifact creation check box in the Advanced Import Options window. This option prevents new artifacts from being created during the import. |
|
Select a target folder for each new specification during an advanced import When you use the Advanced option to import requirements from a ReqIF file, you can select a different target folder for each new specification. Image of the folder options for new specifications: |
|
Select which specifications in a package to import When you use the Advanced option to import requirements from a ReqIF file, you can choose which specifications in a package to import to the current project or component. When you hover over a specification in the import wizard, a preview window shows details about the specification and the artifact types in it. Image of specification details: Image of artifact type details: |
|
Upload packages with multiple .reqifz files You can now upload a package (.zip file) that contains multiple .reqifz files. If you use the "Import requirements from a ReqIF file (Advanced)" wizard to import the package, the import settings apply to all files in the package. |
|
Reviews |
Abstentions are shown in the overall review status When you view the overall status for a review, the hover preview card now shows abstentions. Image of the hover preview card for a review: |
On review pages, sort and resize columns or set the page size Reviews have two pages: Participant's Review and Overall Review. On these pages, you can now sort or resize the table columns or set the page size to 10, 25, 50, 100 or 200. When you change any of the tables, your changes are preserved across sessions so that the next time you start your browser and open a review, the same sort column, column widths, and page size are displayed. These tables have a menu where you can set the page size, reset the page size to the default value, reset the columns to their default widths, and remove the sort column if one is present. For artifact tables, a Clear Sorting button appears beside the menu when a sort column is present. Image of an artifact table with a resized column, a sort column, and an open menu: |
|
Only comments specific to a review are printed When you print an artifact in a review and include comments, the report now prints only comments that are specific to the review. Image of printing an artifact in a review: |
|
Usability enhancements |
All Projects page has a page navigator for over 100 projects The All Projects page now has a page navigator when over 100 projects are displayed. You can use the page navigator at the top of the page to see your projects in increments of 100. Image of the page navigator on the All Projects page: |
Consistent behavior for context menus |
|
Consistent color for selected tabs The color of the horizontal line that appears under the tab when you select All, Collections, or Modules is now consistent with the color for other tabs. |
|
Help for search operations Context-sensitive help is now available for these search operations: quick search, full-text search, and module find. Image of the quick search context-sensitive help: Image of the full-text search context-sensitive help: Image of the module find context-sensitive help: |
|
Improved handling for empty collections Previously, when you opened a collection that didn't contain any artifacts, this message was displayed: No artifacts match the selected folder or filter. Now, a page is displayed that's similar to the page for empty modules. On this page, you can either create a new artifact or insert an existing artifact into the collection. Image of an empty collection: |
|
Messages are displayed when no results are found The Modules and Collections pages now provide helpful information and links when no results are found. For example, on the Modules page, if you perform a query such as Folder is any of MyFolder and the query does not return any results, the following message is shown in the results area: No modules match the selected folder, view, or filter. Show all modules. (Did you mean to look in All Artifacts?) "Show all modules" is a link that removes all filters and selections and shows all modules. "All Artifacts" is a link that opens the All page and applies any filters or selections from the Modules page, which, in this example, shows all the artifacts in the MyFolder folder. The Collections page also shows similar messages when no results are found. Messages are also displayed if you open a module or collection and select a folder, view, or filter that doesn't return results. Image of empty results for the Modules page: Image of empty results for the All page: |
|
New icons for adding and removing filters, and collapsing and expanding filters and sidebars The icons for adding and removing filters, and for collapsing and expanding filters and sidebars, were changed to be more consistent and recognizable. Image of the new icons for adding and removing filters: |
|
New menu icon for rows The icon in the row of a grid used to be a pencil icon. Now, the icon is a menu icon to represent that more actions are available than just editing. Image of a row with the menu icon: |
|
Rows stay selected until a dialog box closes When you open a dialog box from the Artifacts page, any selected rows remain selected until you close the dialog box. Image of selected rows in a dialog box: |
|
Show collections in the "Copy/Clone from Project" dialog box When you select artifacts in the "Copy/Clone from Project" dialog box, you can show only collections by clicking the Add Collection button. Image of the "Copy/Clone from Project" dialog box with the Add Collection button: |
|
You cannot create queries that don't make sense You can no longer create queries that request "Link type x must not exist" and then place restrictions on artifacts at the end of type x links. For example, you cannot specify that the "Child of" link type must not exist but that artifacts at the end of "Child of" links must have a severity of High. Existing queries and filters are not affected by this change unless you edit the link type condition from "Not exists" to "Exists" and then back again. |
|
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here. |
© Copyright IBM Corporation 2019 | Contact | Privacy Policy | Terms of Use