New & Noteworthy for IBM Engineering Requirements Management DOORS Next 7.0.2

	Description
Administration	Add an optional comment when ignoring skipped resources As an administrator, you can now add an optional comment when you send skipped resources to the TRS feed ignore list. If you select the Ignore action in the DOORS Next skipped resource section under the TRS Feed Diagnostics tab, you can now include an optional comment. The comment is applicable to all selected resources and can be viewed as a tooltip when you hover over the ignored resource in the TRS feed ignore list section.
	Links for TRS validation logs added to Administration UI Links to view the TRS validation logs are added to the Tracked Resource Set Validation section of the Administration UI.
	TRS feeds 1.0 is removed from the Administration user interface and documents Starting with the 7.0.2 release, the TRS feeds 1.0 is removed from the Administration user interface and documents that are created by adding "/scr" value at the end of the client address.
	When a project area, component, or configuration is archived or restored, TRS change logs are updated with delete or create events Previously, Lifecycle Query Engine (LQE) and other consumer applications that use TRS feeds maintained data of archived project areas, components, or configurations (streams and baselines) and would cause scalability and performance issues due to a large volume of unused data. The reason for this issue is that DOORS Next does not send TRS delete events for items that are in the archived project area, component, or configuration. In this release, when a project area, component, or configuration is archived or restored, TRS change logs are updated with delete or create events. The following points must be considered during this action: System must handle server restart events. System must handle consecutive archive and restore events for the same project area, component, or configuration. System must not create TRS events for invalid states.
Artifacts	Preview: Simplified Create button for creating cross-application ELM artifacts The 7.0.2 release includes a preview of a simplified artifact Create button along with the support for creation of artifacts in other ELM applications. You can enable this preview feature by setting the Enable ELM cross-application create button Advanced Property value as true under the Advanced Properties section. Important: This feature is being provided for preview or feedback purposes only and should not be enabled in a production system. When you enable this preview feature, the artifact Create button appears on the upper right of the UI with a simplified list of items. Image of simplified Create button: When you select an item, the Create Artifact dialog box displays preferred artifact types in the Artifact type list. Image of artifact preferred types: Image of preferred module content: The Create Artifact dialog box is also updated to open the new artifact in a new tab, if the Open check box is selected when creating the artifact. If a project area has associated project areas of other applications, the Create button includes items for creating artifacts in the associated applications. Image of Create button with ELM creation items: For configuration management enabled project areas, DOORS Next and ETM cross-application artifact creation occurs within the context of a global configuration. Image of Create button in a local configuration: When a cross-application item is selected from the menu, the associated projects are listed in the Create Artifact dialog box. The associated project areas are filtered based on the following rules: Project areas that are archived or not visible to the user are filtered out. For a Source project area that is not enabled for configuration management, the target project areas that are enabled for configuration management are filtered out. When in a global configuration context, DOORS Next and ETM target project areas that do not have configurations contributed to the global configuration are filtered out. Image of the cross-application Create Artifact dialog box: The Create Artifact dialog box also includes an option for opening the created artifact in a new tab so that the created artifact is readily available.
	Simplified linking for OSLC link types Drag and drop In the 7.0.2 release, you can drag and drop an artifact within a single artifact editor, dashboard list, module, or links explorer, or onto a work item editor in EWM, or test artifacts in ETM. You can use the drag handle in the artifact editor to drag the item. The drag handle also appears in the links explorer when you hover over the artifacts. Image of the artifact editor: Image of links explorer: You can drag the artifact into another tab or window that uses the same browser instance and drop the artifact into an editor or grid view. When you drag an artifact over an artifact editor, a drop target is displayed. Image of the drop target for single artifact editor: Image of the drop target for module: Image of the drop target for links explorer: When you drop an artifact on the drop target, you can create links between the artifacts. You can select the link types from the Create Link dialog box and then click Create Links. Image of the Create Link dialog box: You can select artifacts in a module or in an artifact list and drop them to create links to multiple artifacts. Image of drag and drop multiple: Copy and paste You can use the existing Copy option in a module or artifact list, and the existing Paste As Link option on another artifact to create a new link. The link creation feature works between the ELM applications, where the project areas in these applications are registered with each other. You can use the new menu options of Copy and Paste As Link in a single artifact editor to carry out the same operations. Image of Copy option in the single artifact editor: You can use the following keyboard shortcuts for the copy-and-paste feature everywhere drag and drop is available: Copy Link: Ctrl+C (Windows) or Command+C (Mac) Paste as link: Ctrl+Shift+V (Windows) or Command+Shift+V (Mac) Note: The drag-and-drop and copy-paste features for creating links are supported for all the OSLC link types that are supported in the EWM, ETM, and DOORS Next applications. You cannot link artifacts between different global configurations. If you select a configuration in the EWM application, you cannot create a link to another artifact in a different global configuration. Image of the error when trying to create a link to a different configuration:
Build	RRCx converter is removed from the build RRCx objects are not supported in DOORS Next from the 7.0 release onward. The RRCx converter is no longer required and is removed from the build and application code. The build size is now reduced by approximately 200 MB. The following build folders and files are now removed from the build directory: server\rrcweb server\logs\converter.log server\conf\rm\provision_profiles\rrcweb-rrcx server\conf\rm\sites\com.ibm.rdm.web.rrcx.updatesite*
Configuration Management	Create a configuration comparison report In the 7.0.2 release, you can create a configuration comparison report that contains the differences between two related configurations, baselines, or change sets. The compare utility is enhanced so that you can create the comparison report by clicking Print Report. Image of the compare utility: You can select different options when creating a report and select the required output format in the Print dialog box. The following options are available during report creation: Component properties Folders Artifacts Change sets You can select one of the following output formats: PDF Word
Modules	Audit History report template now supports modules In previous releases, the Audit History report template did not support modules. The template worked only on stand-alone artifacts. Starting with the 7.0.2 release, the template can now be used to generate a history report of a module. Additionally, the following enhancements are done related to the Audit History template: For projects that are enabled for Configuration Management, each change in the report includes the name and URI of the associated change set. Each artifact that is reported includes its artifact ID. Any changes that are related to an artifact in a module shows the artifact that is changed. The report wizard includes an additional Boolean parameter named "Show only Module Structure change". This parameter provides an option of either generating a full history report, or a smaller report that includes structural changes related to the module. Miscellaneous defect fixes related to the template. Also, the Publish API with query parameter “history=true” is now enhanced to return the associated change set and the associated module artifact.
People picker	Smart people picker component A new people picker component is now introduced as part of the ongoing user experience transformation and alignment with IBM's open source Carbon Design System. The people picker is a dialog box for selecting users and can be used for assigning an owner or a set of subscribers to an artifact. The new people picker is common across the following applications: DOORS Next Engineering Insights Engineering Test Management Engineering Workflow Management (including Rhapsody Model Manager) Global Configuration Management Jazz Team Server The following improvements are included over the classic people picker component: Access control scoping of users Only the relevant users are shown as defined in the Access Control setting of the current project area. For instance, if read access is set to Members of the project area hierarchy, then you can see only project area and team area members in the search results. Recent users In addition to the current user, you can access the 10 most recently selected users. Managing multiple users Existing users are preselected in the dialog box. You can add new users or remove existing users. Previously, the people picker only supported addition of new users. Now, you can manage an existing selection set in a single step. Note: The classic people picker component is not entirely replaced. You can still use it in the Administration UI, and for selecting users when querying and filtering because these use cases require access to all historical users. Image of the new people picker component, single-user mode: Image of the new people picker component, multiple-user mode: Image of the classic picker component (for comparison):
Reviews	Email notification is not sent to the archived users for any changes in review In previous releases, when you created a review or changed an existing review, an automatic email notification was sent to all the participants of the review. There is a possibility that the participants list can contain users that are archived and no longer require the email notification. Starting with the 7.0.2 release, if there are any updates in a review, the email notification is not sent to the archived users.
RRCx viewer	RRCx viewer is no longer supplied Starting this release, the RRCx viewer is not supplied. You must convert all RRCx artifacts to diagrams before migration. You cannot see the previous diagram in the history
Serviceability	Upgrade the abstracted logging framework The RM logging framework has been upgraded from Log4j 1.x to Log4j 2.13.3. The correlator ID for thread context data, which was present in logs, has changed to trace ID.
	View metadata in application log files for configuration change events You can now view the thread context information in TRS event log files that is related to configuration change events, such as trace ID and user ID.
	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.