Upcoming

This improvement relates to the test grid in  Result. Now users can select multiple tests in the grid (Ctrl + c) and then right-click. The context menu now includes an option to move all of the selected tests to a different project.

Note: Only users who have the permission Can change rd test are able to change the test’s project.

Note: The test may no longer be visible in the grid after selecting a different project. The test’s visibility depends on the filtering and permissions.

This feature relates to the function for manually creating a new test in  Result. Specifically:

• The Create another box is now checked by default.
• There is now also an Empty test check box. If selected, then an empty test will appear after saving

This feature relates to the My profile menu, which can be accessed by navigating to   > My profile. This menu now includes an area called Project Roles. Here you can see which roles you have for which projects.

This feature relates to the Users menu, which can be accessed by navigating to   > Configuration > User management > Users. Now users can click on a cell in the grid and press ‘Ctrl + c’ to copy the cell’s contents.

This feature relates to the MDM requirements grid, which can be accessed by navigating to   > Configuration > MDM > Requirements. Specifically, it relates situations when the requirements have been grouped by test case. Users can now see the state of the MDM test case directly in the test case group row. That means, icons now indicate whether the test case is active ( ) or inactive ( ).

This improvement relates to the MDM test cases, which can be found by navigating to   > Configuration > MDM > Test cases. The workflow for editing multiple MDM test cases has been improved:

1. Select multiple MDM test cases (ctrl. + click) in the overview and then right-click. A context menu will open.
2. Click on  Multi edit. A pop-up window will open.
3. Select an operation from the drop-down list and enter your text into the text field(s).
4. Click on  Change all to apply the changes to all of the selected MDM test cases at once.

The menu can be accessed by navigating to   > Configuration > MDM > Data classifications. Here admins can configure various data classifications, e.g. “Class 0.2 (Holding time 4 years)” and “Class 5.1 (Holding time 30 years)”. Then they can define a default data classification for each of the following model classes:

• Collection
• RdTest
• MdmRequirement
• MdmTestcase
• ProjectRequirement
• ProjectTestCase

This feature relates to the users grid, which can be accessed by navigating to   > Configuration > User management > Users. It is now possible to click on a user in the grid and then click on   to expand a side panel. The information in the side panel is read-only. It corresponds to the information found in the My profile area.

• * for multiple characters.
• ? for a single character.

This improvement relates to the requirements grid in  Project. Specifically, it relates to situations when users view the status of multiple requirements. In the past, the Status summary did not account for requirements without a status.

Example: The image below compares the old status summary (left) and the new status summary (right). In both cases, there is 1 red requirement, 4 green requirements and 3 requirements without a status.

Previously, plotting for such channels ended in an error. Now a sampling interval of “1” is assumed as a fallback, analogous to the fallback if no sampling interval is specified at all.

This improvement relates to the test attachments in  Result, i.e. the tabs:

• Photos
• Videos
• Documents
• Channels
• Measure data
• Events

The grids now have columns Created and Changed, which display the timestamp when the test attachment was originally created and when it was last modified. If these columns are not initially visible, then they can be displayed by clicking on   and then selecting  Choose Columns from the context menu.

This improvement relates to the menu for data classification and model defaults, which can be accessed by navigating to   > Configuration > MDM > Data classifications. There is now a context menu, with options that are specifically for edit mode.

If edit mode is not activated (left image), then the context menu includes the following options:

•  New: Opens edit mode and adds a new line to the grid.
•  Edit: Opens edit mode. The line in the grid can then be edited further.
•  Delete: Deletes the data classification.

If edit mode is activated (right image), then the context menu includes the following options:

•  New: Adds a new line to the grid.
•  Cancel edit: Closes edit mode without saving. All changes will be lost.
•  Reset all changes: Resets all of the edited cells to their original values. Edit mode stays open.

This improvement relates to the MDM test cases, which can be found by navigating to   > Configuration > MDM > Test cases. Now when users right-click on a test case and select  Duplicate from the context menu, a pop-up window appears. In this pop-up window, users can specify how the individual requirements should be treated.

• Take over as duplicate: The requirement will be copied and the word (Copy) will be appended to its name. The copy will be included in the new test case.
• Take over as reference: The requirement will be referenced in the new test case.
• If neither option is selected, then the requirement will not be included in the new test case.

Building on the license management system, feature access checks are now integrated into the permission layer. This prepares the system to enforce feature restrictions based on license status in future updates. The integration is currently inactive to allow for a smooth rollout.

This fix relates to the documents area in  Project. Specifically, it relates to the column on the far left of the grid, which displays the document’s upload status for a brief moment while the document is being uploaded. In the past, there were options to sort this column in ascending and descending order. However, since the column is almost always empty, these options did not make any sense and led to errors. Therefore, the options have been removed.

This fix relates to the requirements grid in  Project. Specifically, it relates to situations when users view the status of multiple requirements. In the past, the Status summary was not displayed if exactly two project requirements were selected. This behavior has been fixed.

This fix relates to the product variants in  Project. In the past, when duplicating an existing product variant, users were incorrectly redirected to the  Result dashboard, instead of to the duplicated variant’s edit screen. This behavior has been fixed.

This fix relates to the Projects and collections area and to the presets in  Result. In the past, the projects 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 projects were selected for which presets. This behavior has been fixed.

This fix relates to the area for creating test templates, which can be accessed by navigating to   > Configuration > Result > Templates. While creating a template, users specify the attributes that should be set for new tests. Optionally, users can also specify the attribute values, but doing so is not required. In the past, an error occurred if the attribute value field was left empty. This behavior has been fixed.

This fix relates to the collections in  Result. In the past, when right-clicking on a test in the grid, the context menu entries Add to collection and Remove from collection were not always enabled when they should have been. For example, if a test was part of a collection, the option to remove it was sometimes grayed out. This behavior has been fixed.

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.

In the past, errors occurred when using a quick filter in requests where no quick filter columns were defined or requested (e.g. in grouped SSRM states). This has been fixed. Quick filters can now be present in the request without triggering a failure, even if no matching columns are available. In those cases, filtering simply won’t be applied.

This fix relates to the MDM test cases, which can be accessed by navigating to   > Configuration > MDM > Test cases. In the past, when users duplicated a test case, the Discipline field was not copied. 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.