Upcoming

1. Select multiple requirements in the  Project requirements grid (Ctrl + click).
2. Right-click and select the option  Export summary from the context menu.
3. A summary of all the selected requirements will open in a pop-up window. You can download the summary in PDF format and then save it in a third-party system.

Alternative: Rather than manually selecting requirements in the grid (as described above), users could also group the requirements, e.g. by test case, and then right-click to export a summary of all requirements in the group.

This feature relates to the Comment and Description fields that are displayed in the side panel of the requirements grid in  Project. Users can now format these fields with Markdown syntax. For example, users can create clickable URLs and links, write lists, add lines of code and highlight text in bold or italic font.

This feature relates to the MDM requirements, which can be found by navigating to   > Configuration > MDM > Requirements. Specifically, it relates to situations when the requirements were grouped by test case. Now users can right-click on a group to access the window for editing multiple MDM requirements. Here users can edit all of the requirements within the group.

This feature relates to the MDM test cases, which can be found by navigating to   > Configuration > MDM > Test cases. Specifically, it relates to the new workflow for editing multiple MDM test cases. The pop-up window now includes a Discipline area, where users can edit the disciplines of multiple MDM test cases at once.

• The function for editing multiple MDM test cases, which can be accessed by navigating to   > Configuration > MDM > Test cases.
• The function for editing multiple MDM requirements, which can be accessed by navigating to   > Configuration > MDM > Requirements.

Users can now click on   to display the pop-up window in full-screen. This is particularly helpful, e.g. when editing longer texts or when using attributes with longer names.

This improvement relates to the add-ons page, which can be accessed by navigating to   > Configuration > Add-ons. The list of add-ons has been redesigned. This is advantageous for two reasons:

• It gives the application a more consistent look and feel, as the layout is also used in other menus.
• The new layout has additional features, such as the ability to filter and sort columns.

The menu can be accessed by navigating to   > Configuration > MDM > Disciplines. Here admins and key users can create and manage disciplines such as “Crashworthiness”, “Fatigue” and “Pedestrian safety”. These disciplines are then available to select in other areas of the system.

This fix relates the status report templates in  Project. Specifically, it relates to the page where users can add templates to a project. In the past, there was a checkbox in the header, which allowed users to globally select/deselect all templates. This checkbox was removed because it was not working correctly.

This improvement relates to the test details panel in  Result. Specifically, users can now click on   to switch to the list view, then click on the   symbol in any column header and select the option Group by [Column name]. In the past, this grouping option was only available for some of the column headers.

This improvement relates to the Projects and collections area and to the presets in  Result. In the past, the selection state was not stored for the preset. That means, when switching between several different presets, the system did not “remember” which projects and collections were selected for each preset. This has been improved.

This improvement relates to the Set as project status feature in  Result. In the past, users sometimes received an error message Matching failed when starting the feature. To fix this problem, the performance was improved when matching attributes against multiple context conditions.

This improvement relates to the MDM test cases, which can be found by navigating to   > Configuration > MDM > Test cases. Specifically, it relates to the window for creating or editing an MDM test case. Now when users click on the Discipline field, they will see the disciplines listed in alphabetical order.

This improvement relates to the process of copying a:

• MDM requirement
• MDM test case
• Project requirement
• Project test case

While creating a copy, users see a pop-up window where they can enter a name for the copied object. In the past, this name had to be unique. However, after creating the copy, users were able to edit it and give it a non-unique name. This inconsistent behavior has been changed. Users are now able to create copies with names that already exist in the system.

This improvement relates to the pages for creating, editing or duplicating objects in  Result and  Project. For example, the page for editing test details in  Result and the page for editing a requirement in  Project. All edit pages were compared and modified for consistency as needed. The pages now all follow the same design guidelines, so that they all have the same look and feel.

This improvement relates to grids, e.g. the test grid in  Result and the requirements grid in  Project. Specifically, it relates to situations when users group the data and then click on   to expand a group. In the past, if the user then added a second grouping level, the previously expanded group would automatically collapse again. This behavior has been improved. When adding or changing grouping levels, the system now “remembers” which groups were already expanded.

This fix relates to the process of adding MDM test cases to a project. In the past, the buttons were not correctly aligned in the upper right corner of the grid. This has been fixed.

This fix relates to the side panel in  Project. Specifically, it relates to the Project Requirements area, which is visible if one test case was selected in the grid. In the past, this area displayed the MDM requirements instead of the project requirements. This has been fixed.

This fix relates the status report templates in  Project. In the past, users were only able to add templates to a project or remove templates from a project, if they also had permission to modify the template. This requirement was incorrect and it has been fixed.

This fix relates to the test grid in  Result. In the past, the column filters sometimes incorrectly displayed the text No values. This happened after the user set a specific combination of filters. This behavior has been fixed.

This fix relates to the Projects and collections area in  Result. In the past, when a user clicked on   and added projects, these projects were not always selected ( ) in the workspace afterwards. This behavior has been fixed.

This fix relates to the Projects and collections area and to the presets in  Result. In the past, the collections that were selected in the Projects and collections area were not stored for the selected preset. That means, when switching between several different presets, the system did not “remember” which collections were selected for which presets. This behavior has been fixed.

This fix relates to the test details panel in  Result. Now, if no mass data is available, e.g. if there are no photos to display, the context menu will not display options to open the carousel or download the data.

This fix relates to the page for editing test attributes in  Result. In the past, users did not see an error message if they entered an invalid value. For example, users were able to enter text in situations when only numerical values should have been accepted. This behavior has been fixed. Users now see an error message if they enter an invalid value.

This fix relates to areas where check boxes are used ( ). In the past, it was only possible to select multiple options if clicking directly on the check boxes. If clicking anywhere outside the check box, the selection was reset. This behavior has been fixed.

This fix relates to the page for editing global roles, which can be accessed by navigating to   > Configuration > User management > Global roles and then by right-clicking on a role and selecting  Edit from the context menu. In the past, when clicking on the expand ( ) or collapse ( ) button in the Permissions area, the user was redirected back to the overview and all changes were saved. This behavior has been fixed. The buttons now work as expected.