0.60.0

This feature relates to the project test case side panel, which can be accessed by navigating to the requirements grid in  Project, clicking on a test case in the overview and then clicking on  . The Attachments panel now displays the attachments that were uploaded for the corresponding MDM test case. Users can download these attachments here.

This feature relates to the documents area in  Project. The area now uses a different upload component, which provides additional functions. Specifically, users can now:

• Drag and drop files to upload
• Individually hide and display column headers
• See the file type and size

This feature relates to the requirements grid in  Project. The grid now includes a column called MDM state. The icon   is displayed in this column if changes were made to the corresponding MDM requirement.

Example of use: When users see this icon, they know that changes were made. They can then compare the project requirement with its MDM equivalent and adopt the changes into the project as needed.

This feature relates to the collections in  Result. Now when users select a collection, their selection is remembered as a so-called “client state”. That means, when users refresh the test grid (or close and reopen the test grid), their selected collections are loaded again.

This feature relates to the presets in  Result. Specifically, it relates to the list from which users can select a preset. In the past, users were able to see and select presets for any discipline, rather than only for their own discipline. This behavior has been fixed.

This feature relates to the test details page in  Result. The Overview section now includes an  Edit button on the right side of the screen. Clicking on this button opens a page where a different project can be selected.

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 test grid in  Result. The context menu now includes an option to change the test’s 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 test grid in  Result. Specifically, it relates to the filter options, which appear when clicking on the   icon in the header. The filter options Blank and Not Blank were added.

This feature relates to the Set as project status function in  Result. The workflow has been extended as follows:

1. Select one or more tests in the grid and click on Set as project status in the context menu.
2. A pop-up window called Select status target opens:
   • Project: Select one single project. The list of projects is grouped between “matching” projects first and “not matching” projects second. If all selected tests belong to the same project, then this project is automatically selected here. The selection can be changed as needed.
   • Template: Here you see all of the templates in the selected project. Select one single template or select the option “Overall scope”.
   • Base report: Specify whether the report should be based on an existing report.
3. Click on Continue, and complete the rest of the workflow as you are accustomed to.

In order to easily update collections with new tests or remove tests from a collection, the following GraphQL mutations were added:

• addTestsToCollection
• removeTestsFromCollection

Via envConfig.metrics.enabled it is now possible to enable the creation of application metrics by Prometheus (django_prometheus). Default is false. Previously, the metrics were always created.

User accounts can either be marked as active or inactive. In the past, inactive users were able to log in via OIDC. When doing so, their user account was automatically activated. This behavior has been changed in two ways:

• Inactive users are no longer able to log in, even if authentication (database, OIDC) is successful. Instead, inactive users see a message, which informs them that their account is deactivated and they should contact an administrator.
• User accounts can now only be activated/deactivated manually.

This feature relates to the jobs grid, which can be accessed by navigating to   > Configuration > Jobs or by clicking on the   symbol in the toolbar. Users can now click on a cell in the grid and press “Ctrl + c” to copy the cell’s content. For example, users could copy the name of a test in the Comment column and then filter for the test with that name in the test grid.

This feature relates to the following grids:

• The project requirements grid
• The MDM requirements grid
• The MDM test cases grid

If a grid has multiple grouping levels, then it can be quite time-consuming to open each group individually. This feature improves the workflow by allowing users to simultaneously expand all groups within a selected level. Users simply right-click on a grouping level and select  Expand.

This feature relates to the MDM requirements grid, which can be accessed by navigating to   > Configuration > MDM > Requirements. Now if users select a test case in the grid and click on   to expand the side panel, they will see detailed information about the MDM test case.

This feature relates to the following pages:

• The page for editing users, which can be accessed by navigating to   > Configuration > User management > Users and then right-clicking on a user account and selecting   Edit from the context menu.
• The page for editing groups, which can be accessed by navigating to   > Configuration > User management > Groups and then right-clicking on a group and selecting   Edit from the context menu.

The sections at the bottom of these pages were made collapsable. That means, e.g. users can now click on the section Global roles or Additional permissions to expand or collapse the section as needed. Chips were also added to indicate the number of selected objects within each section. In the example image, the user account is assigned to 2 groups, 1 global role and 0 additional permissions.

This feature relates to the users grid, which can be accessed by navigating to   > Configuration > User management > Users. The grid now includes two new columns: Company and Contractor. The fields have the following function:

• The company information is required to apply for a license on the license server.
• The contractor field clarifies on whose behalf the user is acting.

Note: These fields can either be filled manually when creating/editing a user account, or they can be populated automatically when logging in via OICD.

This improvement relates to the list of user groups, which can be accessed by navigating to   > Configuration > User management > Groups. The list of user groups has been changed to an AG grid. This is advantageous for two reasons:

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

Navigate to   > Configuration > User content to manage user-specific and discipline-specific settings. For example, here you can manage views, plotting templates or add-on settings. The user content is automatically grouped by tags.

Example: In the image, you see all the different views that were created for the project requirements grid. The overview displays the following information about each view:

• Name: The name of the view.
• Created at / Modified at: When the view was created and last modified.
• Owner: The person who created the view.
• Access: Whether the owner shared the view with other users.
• Discipline: Which disciplines the view was shared with.

Models are separated into multiple parts on the server side. This sometimes creates inconsistencies. For example, when a user reports a value for a requirement or updates its thresholds, the requirement itself should also be updated. In the past, this was not always the case. That means, e.g. the requirement’s ‘updated_at’ time was not always correct. This behavior has been fixed.

Workers can now be configured to scale up or down based on their load (worker.server.idleLoadThreshold), rather than only based on the execution of the last job (worker.server.idleTime). This reduces unnecessary scaling in case of short running jobs.

This improvement relates to the following context menus:

•   > Configuration > MDM > Requirements
•   > Configuration > MDM > Test cases

In the past, these context menus included an entry called  Copy. The entry has been renamed  Duplicate, since this wording is used in other areas throughout the system.

This improvement relates to the product variants grid in  Project. In the past, the columns State and Description had a fixed width. That means, for example, users could not resize the description column to see the entire text of longer descriptions. This has been improved.

This feature relates to the requirements grid in  Project. In the past, there was an option called Quickfilter within the header area. This option was not functional and it has therefore been removed.

This fix relates to pop-up windows, such as the Edit tests window in  Result. In the past, users were no longer able to maximize the window after having resized it. This behavior has been fixed.

This improvement relates to the presets, which can be accessed by navigating to   > Configuration > Result > Presets. Now users can click on a preset in the overview and then click on   to expand a side panel. The side panel displays detailed information about the preset. This information is read-only.

The button Reset grid to preset ( ) is only functional in the  Result test grid. The button is irrelevant to all other grids and has therefore been removed. Specifically, the button has been removed from the following grids:

• Project
  • Requirements
  • Product variants
• MDM
  • Attributes
  • Requirements
  • Test cases
  • Attribute value lists
  • Attribute values
• Configuration
  • Project > Status report templates
  • User management > Users
  • Jobs

Note: The button is still included in the  Result test grid. If a user modifies the test grid, then they can click on this button to reset the grid back to its original appearance as defined by the preset.

This improvement relates to grids that can be configured and saved as “views”, i.e.:

• The project requirements grid
• The test results grid
• The MDM requirements grid
• The MDM test cases grid

The view now controls how wide each column is. That means, you can resize specific columns such as the name or description and then save the configuration as a view. Later, when loading the view, the column width is remembered. There is no need to resize the column each time you load the view.

This improvement relates to the MDM test cases, which can be accessed by navigating to   > Configuration > MDM > Test cases. Specifically, it relates to external MDM test cases, which you can find by setting the filter ( ) in the Source column to External.

Users should not be able to modify external MDM objects. However, in the past, users were able to upload attachments for external MDM test cases via the side panel. This behavior has been fixed.

This feature relates to product variants in  Project. Specifically, it relates to the window where users can assign product variants to test cases.

• The window now has an expand icon ( ) in the upper right corner. Users can click on this icon to maximize the window.
• The window can now be resized as needed. Users can click and drag the lower right corner to resize the window.

This improvement relates to the users grid, which can be found by navigating to   > Configuration > User management. Specifically, it relates to the Last login column. In the past, when users clicked on the   icon, they saw filter options that were suitable for texts. This has been improved. This column now has filter options that are suitable for dates.

This improvement relates to AG grids, such as:

• The project requirements grid
• The test results grid
• The MDM requirements grid
• The MDM test cases grid

Specifically, this feature relates to the side bar, which expands when users click on   on the far right side of the grid. The font size has been decreased in the Views area of the side bar. This allows a greater number of characters to be displayed per line.

This improvement relates to the following pages:

•   > Configuration > MDM > Attribute components
•   > Configuration > MDM > Attribute value lists
•   > Configuration > MDM > Attribute values

These pages now include a Source column, which indicates whether the data is internal or external. Internal data was added to the overview manually. This data can be edited further or deleted. External data was imported into the overview. This data is read-only, meaning that it can not be edited, deleted, duplicated, or activated/deactivated.

This improvement relates to the My profile page, which can be found by navigating to   > My profile. Users can now see profile information such as their user name, disciplines, roles, etc. This gives users an overview of their permissions, so that they can clarify any licensing issues and access support-relevant information regarding their account.

This improvement relates to the Project members area in  Project. The grid’s appearance was changed to more closely match the grids in other areas. Specifically:

• When users right-click on an entry, they now see a context menu with the options Add and Delete.
• The   icon was removed from the grid since it is now located within the context menu.

This change relates to the requirements grid in  Project. Specifically, it relates to the context menu, which appears when you right-click on a requirement or test case in the grid. In the past, the context menu displayed options for both requirements and test cases. This has been improved as follows:

• If you right-click on a requirement, the context menu only displays options for requirements.
• If you right-click on a test case, the context menu only displays options for test cases.

The permissions system has been refactored for clarity and consistency. While behavior remains mostly unchanged, nested object permissions are handled more restrictively. Some adjustments to existing configurations may be needed - see the table for details.

The new logo is visible in the following areas:

• Toolbar
•   > About
• Loader (reloading the page)
• Favicon (Browser tab)

This fix relates to the project members grid in  Project. Specifically, it relates to the filter options, i.e. the blank lines directly below the column headers and the   icons. In the past, these filter options were temporarily disabled in the grid. This has been fixed. The filter options are now visible again.

This fix relates to edit pages, e.g. the page for editing requirements in  Project. In the past, users received an error when they tried to add a context attribute of the type “Number”. This behavior has been fixed.

This fix relates to the product variants area in  Project. Specifically, it relates to the edit page, which can be accessed by right-clicking on a product variant in the grid and selecting  Edit. In the past, no context values were displayed on the edit page, even if they were configured. This has been fixed. Context values are now visible again.

The parameter as_of is used, for example, when filtering by status reports. An error was therefore displayed in the application when working with status reports.

This fix relates to the thresholds of MDM requirements. In the past, users received an error message if they tried to change multiple thresholds at once. For example, an error was displayed upon saving, if a user tried to change the thresholds as follows:

• Change the first threshold from 0 ≤ x < 1 to −∞ ≤ x < −1
• Change the second threshold from 1 ≤ x < ∞ to −1 ≤ x < 0

This behavior has been fixed. Users can now change multiple thresholds at once.

This fix relates to the Project members area in  Project. In the past, the delete button ( ) was not working correctly for user groups. This behavior has been fixed. It is now possible to delete user groups from the grid.

This fix relates to the project members grid in  Project. In the past, the grid displayed “ERR” if there was a user with multiple roles. For example, if the user “John Doe” was assigned to the project with the role “Project Manager” and then also assigned to the project with the role “Project Developer”. This behavior has been fixed.

This fix relates to the requirement status summary in  Project. Users can access the status summary by selecting multiple requirements in the grid and then clicking on   to expand the side panel. In the past, the summary chips were broken, i.e. they were too narrow and they did not include any text. This has been fixed. The summary chips are now displayed correctly again.

This fix relates to the page for editing a project test case. In the past, no requirements were displayed when expanding the Project Requirements area. Additionally, the browser console displayed an error. This behavior has been fixed.

This fix relates to the requirements grid in  Project. In the past, when a user modified a project requirement, the Modified by column was not updated to show who made the change. This behavior has been fixed.

This fix relates to the page for creating a new product variant. The Discipline field is marked as mandatory on this page. However, in the past, it was possible to create a new product variant without selecting a discipline. This behavior has been fixed.

This fix relates to the requirements grid in  Project. In the past, the requirements grid displayed ERR when trying to open a status report. The browser console displayed an error relating to ‘duplicate row ids’. This behavior has been fixed.

This fix relates to the requirements grid in  Project. Specifically, it relates to the status report templates area on the left and the side panel on the right. In the past, if users opened both of these areas, then the components overlapped and made the grid in the middle unusable. This behavior has been fixed.

This fix relates to the status report panel in  Project. In the past, the width of this panel was incorrectly reduced, making the information less accessible to users. This has been fixed. The status report panel is now displayed with the correct width again.

This fix relates to the requirements grid in  Project. In the past, users received an error if they tried to sort or group the requirements in the grid by certain context attributes. Specifically, the error occurred when sorting/grouping by context attributes whose attribute identifiers contained whitespaces. This behavior has been fixed.

This fix relates to the page where users can compare a project test case or requirement to its MDM equivalent. Users are now only able to access this page if they have permission to change project requirements or project test cases.

This fix relates to the requirements grid in  Project. In the past, users sometimes received a 500 error when they tried to access the requirement’s history in the side panel. This behavior has been fixed.

This fix relates to the collections in  Result. In the past, users were not able to create collections if they only had the permission Can add collection. They additionally needed to have the permission Can change collection. This behavior has been fixed. Users no longer need the change permissions in order to create a collection.

This fix relates to the collections in  Result. In the past, when users created a new collection, it automatically included all tests. This behavior has been fixed. Collections now only display the tests that were added to them.

This fix relates to the Events tab in  Result. Specifically, it relates to the options in the context menu. In the past, the context menu listed the options Open with 3d viewer and 3D Viewer. The duplicate entry has been removed.

This fix relates to the Evaluate tests function in  Result.

This fix relates to add-ons that are schedulable. In the past, such add-ons failed to the upload. This behavior has been fixed.

This feature relates to the attributes in  Result. Specifically, it relates to the Attributes tab within the test details panel and also to the Attributes area within the test details page. In the past, the test attribute’s isocode was sometimes displayed in the Name column rather than the attribute’s name. This behavior has been fixed.

This feature relates to the Edit tests window in  Result. In the past, the functions for maximizing and resizing the window were not working correctly. This behavior has been fixed.

• The window can be maximized again by clicking on the icon ( ) in the upper right corner.
• The window can be resized again by clicking and dragging the lower right corner.

This fix relates to the test grid in  Result. Specifically, it relates to situations when users grouped the tests by a column header. In the past, when users expanded a group, the word “null” was displayed in the Group column. This has been fixed. The column is now empty.

This fix relates to the  Result test grid. Specifically, it relates to the  x button, which turns red if column filters are set. Users can click on this button to clear all column filters. In the past, the button did not turn black again when the column filters were cleared. This behavior has been fixed. The button is now displayed with the correct colors.

This fix relates to the filters in the  Result test grid. In the past, the filter failed to load values in combination with the Blanks filter. This behavior has been fixed.

This fix relates to the toolbar in  Result. Specifically, it relates to the menu item called Dashboard, which is visible from within the test details page. In the past, when users clicked on this menu item, its name changed to Result. The menu item has now been renamed for clarity.

This fix relates to periodic add-ons that use crontab syntax for scheduling. In the past, the labels Minute, Hour, Day of Month, Month and Day of week were not displayed correctly. The labels were not readable. This behavior has been fixed.

This fix relates to the videos that are uploaded in  Result. In the past, the video thumbnail would not be created and the conversion to a web-compatible format would fail with the error message “moov atom not found.” This issue only happened in certain cases. It was caused by incomplete file flushing during temporary file creation. The problem has been resolved by ensuring all video file data is properly flushed to disk before processing, allowing for accurate video metadata parsing.

This fix relates to situations when an attachment is uploaded using the createRdTestAttachment API endpoint. In the past, the given name was not taken into consideration. Instead, the full file path was used as the attachment name. This behavior has been fixed.

This fix relates to the access tokens, which are displayed under   > Configuration > User Management > Access tokens. In the past, the grid displayed the word ‘ERR’ instead of the access tokens. This behavior has been fixed.

This fix relates to the jobs list, which can be accessed by navigating to   > Configuration > Jobs. Specifically, it relates to the filters that appear when clicking on the   icon in a date column, e.g. Created at. In the past, the filter type Equals did not work for dates, and the filter type Greater Than behaved like greater than or equal. This behavior has been fixed.

This fix relates to the Groups area, which can be accessed by navigating to   > Configuration > User management > Groups. In the past, group information was not displayed correctly in the list. This behavior has been fixed.

This fix relates to the user edit page, which can be accessed by navigating to   > Configuration > User management > Users and then right-clicking on an existing user account and selecting Edit from the context menu. In the past, the user edit page included a delete button ( ) in the page header. This button has been removed. User accounts can now only be deleted via the context menu in the grid.

This fix relates to jobs that have artifacts (as indicated by the   icon). In the past, the artifact download button was displayed incorrectly. It appeared as %2Fresults.zip instead of results.zip. Additionally, the download file had the name _result.zip instead of result.zip. Both of these issues have been fixed.

This fix relates to the pages under   > Configuration > MDM. That means, it relates to MDM:

• Attributes
• Requirements
• Test cases
• Attribute components
• Attribute value lists
• Attribute values
• Calculation rules

These pages contain a column called Source, where users can see if an object is internal or external. In the past, internal and external objects were treated a bit differently on each page. They have now been made consistent. Internal objects can be edited and deleted. External objects are read-only, meaning that they can not be edited, deleted, duplicated, or activated/deactivated.