0.54.0

This feature relates to the requirements grid in  Project and the MDM requirements grid, which is found under   > Configuration > MDM > Requirements. These views now include a field called Attribute key.

This improvement relates to the Calculation rules view, which can be accessed by navigating to   > Configuration > MDM > Calculation rules. This improvement also relates to the Job detail view, which can be accessed by clicking on   in the toolbar or by navigating to   > Configuration > Jobs. A grouping panel was added to these pages. That means, there is now an area called Drag here to set row groups in the upper left corner of the grid. Users can drag a column header to this area. The data in the grid will be grouped by this column.

This improvement relates to card components, for example the contact data card, which is displayed under   > Configuration > Add-ons > [Open add-on]. The font sizes were decreased and the padding was adjusted, so that the card component better matches the rest of the layout.

This improvement relates to the Apply calculation rule function, which can be accessed by navigating to  Result and right-clicking on a test in the grid. Specifically, it relates to the debug view, which can be accessed by clicking on   on the far right. Now the error’s line number is displayed in both the grid and in the detailed information, which is displayed after clicking on  .

This improvement relates to the requirements grid in  Project. Users can now copy the name of a test case group by clicking on the test case group and then pressing Ctrl+C.

This change relates to the MDM test cases, which can be accessed by navigating to   > Configuration > MDM > Test cases. This change also relates to the project test cases, which can be accessed by opening a project, clicking on Requirements in the left sidebar, right-clicking on a requirement in the overview and then selecting Edit test case [Name of test case] from the context menu. The Discipline field is no longer mandatory. It has been changed to an optional field.

This fix relates to the Apply calculation rule function in  Result. Specifically, it relates to situations when a user corrected an argument in the debug mode and then clicked on the button Calculate again. Afterwards, when saving the calculation, the attributes were not updated as they should have been. This behavior has been fixed. The attributes are now correctly calculated after having used the debug mode.

This fix relates to the test details in  Result. Specifically, it relates to the Events tab. Users can now sort the test events by their numerical value in the column Score.

This fix relates to the Apply calculation rule function, which can be accessed by navigating to  Result and right-clicking on a test in the grid. Specifically, it relates to the debug view, which can be accessed by clicking on   on the far right. In the past, changes were discarded under the following conditions:

• The user modified the input values of a result and clicked on Calculate again.
• The user then modified the input values of a second result and clicked on Calculate again.

In this case, changes to the first result were discarded and only the changes to the second result were saved. This behavior has been fixed.

This fix relates to the requirements grid in  Project. Under certain conditions, the status displayed in the grid was different than the status displayed in the side panel. This happened if:

• User A saved a private status for a requirement.
• User B then saved a public status for the same requirement.
• Under these conditions, user A would see the private status in the requirements grid, and the public status in the side panel.

This behavior has been fixed. Now, if a user has saved a private status, the private status is displayed in both the grid and the side panel.

This fix relates to the requirements grid in  Project. Specifically, it relates to cases when users view the status of a requirement group. In the past, public statuses were not correctly aggregated after their assessment color was manually changed. That means, if the user manually selected a different assessment color, then the group’s color was not correctly updated to reflect the worst status within the group. This behavior has been fixed. The assessments are now correctly aggregated.

This fix relates to the requirements grid in  Project. In the past, quickly switching to the project requirement page and clicking on the Add button caused an error to occur and the addition of test cases failed. This behavior has been fixed.

This fix relates to the Apply calculation rule function, which can be accessed by navigating to  Result and right-clicking on a test in the grid. Specifically, it relates to the debug view, which can be accessed by clicking on   on the far right. In the past, when a user right-clicked on a result, the Debug context matching context menu was grayed out. The context menu remained disabled until the attributes had finished loading. This was misleading as it suggested that the debug context matching was not available. This behavior has been fixed. The context menu is now enabled by default.

This fix relates to the requirements grid in  Project. Specifically, it relates to the logic that determines which requirements a user can see/edit in the grid. The logic works as follows:

1. Disciplines are assigned to each test case and to each user.
2. A user can see a requirement in the grid if the user has the same discipline as the test case in which the requirement is located.
3. If a user is not assigned to any discipline, then the user will not be able to see any test cases.
4. If a test case is not assigned to any discipline, then the test case will be visible to users with any discipline.

This fix relates to the history section of the requirement details, which can be accessed by opening a project, clicking on Requirements in the left sidebar, clicking on a requirement in the overview and then clicking on  . In the past, the history section displayed the correct number of entries, but the content of those entries was sometimes incorrect. This was because the ‘Load-More’ component was working incorrectly for historized models, resulting in duplicates in the history view. This behavior has been fixed. The history section now displays the correct entries.

This fix relates to the project requirement overview, which can be accessed by opening a project and clicking on Requirements in the left sidebar. Now when you expand the Milestones area and select a previous date from the Choose a date field, the thresholds change to display what their values were on the selected date.

This fix relates to the MDM test cases, which can be accessed by navigating to   > Configuration > MDM > Test cases. Specifically, it relates to the numerical range values that are saved in the Context area, for example a speed between 15 and 20km/h. Such numerical range values are now correctly converted from the display unit (e.g. km/h) to base SI units (e.g. m/s) when they are saved to the backend server. Likewise, they are correctly converted from the base SI units (e.g. m/s) to the display units (e.g. km/h) when they are retrieved from the backend server.