0.56.0

This feature relates to the requirements grid of  Project. Specifically, it relates to the function for comparing requirement statuses from one milestone to the next. Now when users click on a milestone, the milestone’s date is automatically entered into the Choose a date field and the requirement statuses change to reflect what their values were on that date.

This feature relates to the test grid in  Result. Specifically, it relates to the Photos tab. Here, users click on   to display the photos as a list, and then select the relevant photos (ctrl. + click). Now, when users right-click, the context menu contains an option called Compare Images. This option allows users to compare images side-by-side. For example, users could compare the changes in various design versions.

This feature relates to the test details page in  Result. It is now possible to edit the test name within the Overview section. Users who have the permission Can change rd test see an   Edit button on the right side of the screen. Clicking on this button opens a page where the name can be edited.

This feature relates to the requirements grid of  Project. Specifically, it relates to the function for sharing views with other users. Now when an admin or key user shares a view, they can select multiple disciplines from the Discipline drop-down list.

Via envConfig.scaling.cpuUtilization it is now possible to change the utilization limit for the application horizontal autoscaling setting. By default, this is now 60.

The feature relates to those menus in  Project and  Result that allow users to select their project from a list. For example, the area for selecting a project in  Project and the Projects and collections window in  Result. Now when users open these menus, they automatically see the Starred projects area, rather than the list of all projects.

This feature relates to the requirements grid in  Project. Now when requirements are grouped by their test case, users can right-click on the grouped level and select the option   Compare test case to MDM from the context menu. This option opens a window where users can see the differences between the project test case and its MDM equivalent. Users can then adopt the differences into the project if needed.

This feature relates to those menus that have a sidebar, e.g. the requirements grid in  Project or the calculation rule dubugging view in  Result. If a user opens the sidebar and/or changes the sidebar width, then these settings are remembered even after the page has been reloaded, i.e. after switching to another page and coming back.

This feature relates to the toolbar in  Project and  Result. The ‘Confidential information’ chip is now displayed with a white outline. This ensures that the chip remains clearly visible, even if the toolbar has a custom color, e.g. for corporate identity purposes.

This feature relates to  Project. Specifically, when adding test cases to a project, users now see an In project column, which indicates whether the test case has already been added. This helps prevent users from accidentally importing the test case twice.

This improvement relates to the calculation rule dubugging view in  Result. When a user changes the input attributes and clicks on the button Calculate again, it can take approximately 2-3 seconds for the values to be recalculated. Now, a loading indicator has been added, which provides feedback to the user and prevents further editing while the recalculation is in progress.

This improvement relates to the requirements grid in  Project. Specifically, it relates to the Context section of the side panel. In the past, float range values were not displayed correctly here. This behavior has been fixed.

This improvement relates to the MDM attribute components, which can be accessed by navigating to   > Configuration > MDM > Attribute components. The list of components has been changed from a material table to an AG grid. This is advantageous for two reasons:

• It gives the application a more consistant look and feel, as AG grids are also used in other menus.
• The AG grid has additional features, such as the ability to filter, sort or group columns.

This improvement relates to the MDM attribute value lists, which can be accessed by navigating to   > Configuration > MDM > Attribute value lists. The list has been changed from a material table to an AG grid. This is advantageous for two reasons:

• It gives the application a more consistant look and feel, as AG grids are also used in other menus.
• The AG grid has additional features, such as the ability to filter, sort or group columns.

This improvement relates to the add-ons that are managed under   > Configuration > Add-ons. It is only possible to upload an add-on as a .zip file. If the uploaded file is not a valid .zip add-on file, then the application will reject the upload and display an error message. The wording of this error message was improved, so that users now have more information about the problem and how they can solve it.

In the past, when saving a preset brick, the user sometimes received a timeout error or the system was unresponsive for several seconds. This performance issue has been fixed.

This improvement relates to the plotting function in  Result. In the past, if the channel data contained non-numerical values such as NOVALUE or NaN, then those values were ignored and the channel file was reduced by the non-numerical entries. This has been improved. The plotting component is now able to handle non-numeric values.

This improvement relates to the test grid in  Result. Specifically, it relates to the function for importing tests. Now, when a user right-clicks in the window Projects and collections, the context menu Import tests is only displayed if the user has the permission Can add rd test.

This improvement relates to the milestones in  Project. The master timeline is now displayed in bold font, so that it is easy to tell it apart from the other timelines.

This improvement relates to the milestones in  Project. In the past, the milestones were implemented with help of the Plotly graphing library. This has been changed. The milestones are now implemented with the ECharts library.

The old customtools-python worker has been removed and the new runner implementation has been enabled by default. The runner is fully backwards compatible and provides new features like auto-scaling and the new .addon.yaml specification including custom docker images and resource reservations for addons.

Strategies for data synchronization vary from customer to customer. Whether and when attachment data (and files) should be loaded should be regulated in the add-on associated with a backend system. The attachments_age_limit_minutes_for_auto_synchronize field has therefore been removed as it provided a too strict definition for customer strategies. The field determined the meta_only parameter in the UpdateTest and GetAttachmentsOfTest task. This parameter has been removed accordingly.

This fix relates to the bes projects, which can be edited by navigating to   > Admin area. In the past, an error message was displayed when saving changes to a bes project. This behavior has been fixed.

This fix relates to the MDM requirements grid. Specifically, it relates to views that have several different grouping levels, e.g. Region > Directive > Test case. Sometimes, after reloading the browser or accessing the MDM requirements grid again, the view displayed these grouping levels in a different order, e.g. Test case > Region > Directive. This behavior has been fixed. The grouping order is now preserved.

This fix relates to the status report templates in  Project. In the past, when a user right-clicked on a status report and selected the option  Derive status report, the error message Failed to derive status report - id: Could not resolve the type was displayed. This behavior has been fixed.

This fix relates to requirements grid of  Project. Specifically, it relates to the function for comparing requirement statuses from one milestone to the next. In the past, when a user applied a column filter and then selected a date in the past, the grid displayed an error message. This behavior has been fixed.

This fix relates to the MDM attribute value lists, which can be accessed by navigating to   > Configuration > MDM > Attribute value lists. In the past, attribute value lists sometimes failed to disappear from the overview after having been deleted. That means, the data was removed in the backend, but it was still visible in the frontend. This behavior has been fixed.

This fix relates to the MDM test cases that are managed under   > Configuration > MDM > Test cases. In the past, if a user opened an internal MDM test case and only changed a setting such as the name or the description, the user was not able to save these changes. The error message Failed to add requirements to test case - General: No selection state changes specified was displayed. The user was only able to save their changes if they also edited the Requirements section. This behavior has been fixed.

This fix relates to the MDM requirements grid, which can be accessed by navigating to   > Configuration > MDM > Requirements. Specifically, it relates to requirements that have multiple values for a context attribute, e.g. a requirement that applies to both the region Europe and North America. In the past, if the requirements grid was grouped by this context attribute, e.g. grouped by the region, then the requirement was displayed in multiple groups, e.g. in the group “Europe” and in the group “North America”. This behavior has been changed. The requirement now appears in a single group, e.g. “Europe, North America”.

This fix relates to the status report templates in  Project. In the past, when a user added a status report template to a project, the template did not automtically appear in the list. Users needed to reload the Requirements page and then expand the status report area again. This behavior has been fixed.

This fix relates to the requirements grid in  Project. Specifically, it relates to the columns:

• Status > Comment
• Status > Access
• Status > User
• Status > Created at
• Status > Reference test
• Status > Reference state

In the past, an error was displayed when users tried to filter, sort or group the requirements by one of these columns. This behavior has been fixed.

This fix comes in two parts: The first part relates to the status report templates that are managed under   > Configuration > Project > Status report templates. In the past, when a status report template was duplicated, the copy was automatically added to the same projects that the parent template was in. This behavior has been fixed. Copied status report templates no longer inherit the projects from their parent templates. The second part of the fix relates to the wording used on buttons and column headers. Slight changes were made for conformity.

This fix relates to the requirements grid in  Project. In the past, the State column was not displayed in the grid. This behavior has been fixed.

This fix relates to the requirements grid in  Project. In the past, when users filtered the requirements by entering text into the Test case column, the results did not always match the filter string. This behavior has been fixed.

This fix relates to the attribute grid in  Result. In the past, the attribute’s key was displayed in the Name column. This behavior has been fixed. The column now displays the attribute’s human-readable name.

This fix relates to the attribute grid in  Result. In the past, the attribute’s raw value was sometimes displayed in the Value column. This behavior has been fixed. The column now shows the attribute’s display value.

This fix relates to the status report templates in  Project. In the past, when a user right-clicked on a private status report and selected the option   Set public, the user could still report a status. That means, the Report Status button was not disabled in the right side panel. This behavior has been fixed. The button is now disabled as soon as the status report is set public.

This fix relates to the test grid in  Result. Specifically, it relates to an error that occurred if the user selected a project in the upper left corner and then clicked on the filter icon in a column header ( ). In this case, the user received the error message Failed to load values. This behavior has been fixed. The list of filter values now loads correctly.

This fix relates to requirements grid of  Project. In the past, browsing through the requirements grid sometimes caused the grid to reload unintendedly. This behavior has been fixed.

This fix relates to the requirements grid in  Project. The thresholds in the side panel are now displayed in the same order as they appear in the grid.

This fix relates to the requirements grid of  Project. Specifically, it relates to the function for comparing requirement statuses from one milestone to the next. Now when users select a date in the past, the requirement’s status from that date is not only displayed in the grid, but also in the side panel.

This fix relates to the requirements grid of  Project. Specifically, it relates to the function for comparing requirement statuses from one milestone to the next. Now when users select a date in the past, the requirement’s status from that date is updated in the grid. In the past, only the aggregated test case status was updating correctly. This behavior has been fixed.

This fix relates to the requirements grid of  Project. Specifically, it relates to the columns Created at and Created by. In the past, these columns were empty. This behavior has been fixed. The columns now show the date when the project requirement was created and the user who created it.

This fix relates to the test grid in  Result. In the past, an error message was displayed when clicking on   for a number column, selecting the filter type Equals or Not Equal, and then entering a number into the field Value. This behavior has been fixed.

This fix relates to the status report templates in  Project. In the past, empty status reports, i.e. reports that don’t have any matching requirements, could be switched from private to public. This behavior has been fixed. Now, when a user right-clicks on an empty, private status report and selects the option   Set public, the error message Failed to publish report - General: Publishing empty reports is not possible is displayed.