2.0.0

This feature relates to the page for editing a project test case. This page now includes a Comment field.

• When an MDM test case is added to a project, the comment from the MDM test case is copied.
• Users can then adjust the comment within the project test case as needed, and make the comment project-specific.
• When a project test case is duplicated, its comment is also duplicated.

This feature relates to the Documents area in  Project. Users can now assign attributes to their project documents. The basic workflow is as follows:

1. Open your project and scroll down to the Documents area.
2. Right-click on a line in the grid and select Add columns from the context menu. A pop-up window opens.
3. Select the attributes that should be displayed in the documents grid and click on Confirm. Each attribute is displayed as a separate column.
4. Click on Edit mode. The grid becomes editable.
5. Double-click on an attribute cell and select the appropriate attribute value(s) from the drop-down list.
6. Click on Save when you are finished.

Users can then easily see which attributes were assigned to which documents. Users can group, filter and sort the documents by their attributes. This helps users manage the project documents more efficiently.

This feature relates to the Documents area in  Project. Users can now enter comments for their project documents. The basic workflow is as follows:

1. Open your project and scroll down to the Documents area.
2. Click on Edit mode. The grid becomes editable.
3. Double-click on a comment cell and enter your comment into the text field.
4. Click on Save when you are finished.

Comments can be used to give background information about a document. For example, users could mark outdated files with the comment “obsolete” or they could specify which dates regulation documents are valid from/to.

This feature relates to the list of projects, which can be accessed by navigating to   > Configuration > Projects. The overview now includes a column called Product variants. Here:

• Users can see the product variants that are assigned to each project. If multiple product variants are assigned to a project, then the values are separated by commas.
• Users can group projects by variant. That means, if multiple product variants are assigned to a project, then the project will appear under each variant.

This feature relates to the list of projects, which can be accessed by navigating to   > Configuration > Projects. The overview now includes a column called Attributes. Here:

• Users can see the attributes that were saved for each project in the project settings area.
• Users can filter and group projects by their attributes. This provides a better overview.

This feature relates to the list of projects, which can be accessed by navigating to   > Configuration > Projects. Now when users right-click on a line in the grid, the context menu includes options to create, edit or delete a project.

This feature relates to the attachment panels in  Result. For example, the tabs for Photos, Videos, Documents, Channels, etc. Specifically, this feature relates to situations when the attachments are displayed as preview images (icon view). While using icon view, users can now select one or multiple attachments (ctrl. + click) and then right-click to open a context menu with additional options.

This feature relates to the Attributes tab in  Result. This tab now has an additional column called Comment. Here users can see the test attribute’s comment.

• The column is editable, which means that users can double-click on a cell and then enter a comment for the test attribute. To do so, the user must have permission to change the rd test attribute.
• Alternatively, users can edit the attribute’s comment from the test details page.

This improvement relates to the attachment panels in  Result, i.e. the tabs Photos, Videos, Documents, Channels, Measure data and Events. Specifically, it relates to situations when using list view. Users can now add custom columns to the grid, which are used for displaying meta information about the attachments. The basic workflow is as follows:

1. Right-click on a cell in the grid and select Add custom column from the context menu. A pop-up window opens.
   • Column name: Enter a name for the custom column. Note: The name may not contain spaces, hashes, quotation marks, semicolons, or SQL comments.
   • Database-field path: Select the meta key that should be displayed in the column. Note: This field has an autocomplete function, which you can use if the list is very long, i.e. if the attachments have a very large number of meta keys.
   • Target data type: Select which type of data the meta key contains, e.g. a number, date or string of characters.
2. Click on  Add when you are finished. The column will be added to the grid.

This feature relates to the Upload CSV file function, which allows users to upload attributes in a CSV file. Users can now enter comments for the attributes directly into their CSV file.

1. Create a CSV file with three column headers (Identifier, Value, Comment). In this CSV file, enter information about as many attributes as needed.
2. Click on Upload CSV file and select the file from its location on your computer.
3. A pop-up window opens. In this window, specify which separator the CSV file uses, whether the CSV file includes a header, and which column contains which information.
4. Click on Add attributes when you are ready to upload the attributes.

This feature relates to the Jobs area, which can be accessed by clicking on   in the upper right corner. The Jobs area now includes a Started at column, which displays the date and time when each job was started. This information is useful because some jobs remain pending for an extended period of time. That means, a lot of time might have elapsed between when a job was created and when it was first started.

In the past, there was no uniqueness check when creating or editing a value list. If there were several different entries for the same system value with different display values, it was not clear which one was being used. Therefore, a uniqueness restriction was added, so that name is unique together with the value_list for MdmAttributeValue.

This feature relates to the MDM attributes, which can be accessed by navigating to   > Configuration > MDM > Attributes.

• The attributes grid now includes a Discipline column, where you can see which disciplines were assigned to each attribute. You can also filter or group the attributes in the grid by their discipline.
• When creating/editing an attribute, you can now assign none, one or multiple disciplines.

Use-case: Disciplines help users manage their MDM attributes more efficiently. Users can assign disciplines to MDM attributes and then group the attributes by discipline for faster navigation and filtering.

The life cycles area can be accessed by navigating to   > Configuration > MDM > Life cycles. Here, admin users can manage life cycles and their states. That means, they can create, edit, activate/deactivate and delete life cycles. The life cycles in the list can be filtered, sorted and grouped as needed.

The cache block allows add-on actions to cache specific files between different action runs. This can be useful for improving performance by persisting dependencies, build artifacts, or similar data across runs.

runner:
  actions:
    default:
      cache:
        paths:
          - "*.json"
          - "docs/*.md"
        when: always
        policy: pull

• cache.paths: Defines a list of relative paths (anchored at the add-on’s working directory) which should be cached.
• cache.when: Configures when the cache should be stored or updated after completion of the action. The default is on_success. This can be changed to always and on_failure.
• cache.policy: Sets if the cache should be pulled (restored), pushed (saved), or both (pull_push, the default).

This feature relates to the life cycles, which can be accessed by navigating to   > Configuration > MDM > Life cycles. The overview now includes a new column, which is pinned to the left and which has a drag handle. This allows users to drag and drop the life cycles, thus repositioning them in the overview.

This improvement relates to the permissions that are necessary for deriving new status reports. Now users have more flexibility when configuring the permissions and dividing up responsibilities. For example, it is now possible to allow developers to derive new status reports, while at the same time preventing them from changing or adding project requirements.

This improvement relates to the attachment panels in  Result, i.e. the tabs Photos, Videos, Documents, Channels, Measure data and Events. Specifically, it relates to situations when using list view. Users can now activate “edit mode” and then edit the cells just like they would an Excel spreadsheet. The basic workflow is as follows:

1. Click on  Edit mode in the lower left corner of the attachment panel.
2. Double-click on a cell in the grid, e.g. a Description cell. The cell becomes editable.
3. Edit the cell as necessary. Continue editing any other cells the same way.
4. Click on  Save when you are finished.

This improvement relates to the following areas:

• The context menu in the test result grid
• The context menu in the test attributes grid

The context menus now follow the same design guidelines as other menus. That means, e.g. the context menus now use the same wording and icons as other menus. This improves the user experience and makes the application more intuitive.

This improvement relates to the column headers in the test grid of  Result. Display units are now shown with special characters and powers. For example, the unit notation m*m*m is now displayed as m³.

This improvement relates to the presets, which can be accessed by navigating to   > Configuration > Preset > Presets. In the past, if a user tried to save an invalid preset, then a generic “Preset could not be updated” message was displayed without any further details. This has been improved. The system now provides specific information about what is wrong, helping users understand and correct issues before trying to save the preset again.

This improvement relates to the disciplines, which can be accessed by navigating to   > Configuration > User management > Disciplines. Users are no longer able to delete a discipline that is currently being used for a preset.

This improvement relates to the collections in the  Result test grid. Specifically, it relates to the process of creating a new collection. In the past, the Discipline drop-down list displayed all available disciplines. That means, the user was able to create a collection in a foreign discipline. This has been improved. The Discipline drop-down list now only displays those disciplines that the user is assigned to.

This improvement relates to the  Result test grid. In the past, when values were copied / pasted into the cells of attribute columns, the values were not displayed until the user reloaded the grid. This has been improved. Pasted values are now immediately visible in the target cells.

Logging was extended to ensure that all downloads (frontend, CLI, API) can be uniquely linked to a specific user ID. This allows users to analyze the triggered downloads as needed, e.g. for security or cost reasons.

This improvement relates to the context menus in the following areas:

• MDM requirements side panel (Attachments area)
• MDM test cases side panel (Attachments area)
• Project overview (Documents area)

The context menus now follow the same design guidelines. That means, e.g. the context menus now use the same wording and icons. This improves the user experience and makes the application more intuitive.

This improvement relates to the model classes, which can be accessed by navigating to   > Configuration > MDM > Data classifications. The model classes were renamed as follows:

This helps users better understand each model class.

Values that differ from the target type and that cannot be converted to it are ignored instead of being acknowledged with an error.

This improvement relates to objects that have an internal/external distinction, e.g. MDM test cases and MDM requirements. Specifically, it relates to situations when users select multiple objects and right-click to access the context menu. The Multi-edit option is now disabled if an external object was selected. The option is disabled because external objects are read-only, meaning that they can not be edited, deleted, duplicated, or activated/deactivated.

This improvement relates to the announcements page, which can be accessed by navigating to   > Configuration > Announcements. The list of announcements 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, sort or group columns.

This improvement relates to the workflow for duplicating objects, such as MDM attributes, requirements, test cases, product variants, templates, etc. In the past, when a user selected Duplicate from the context menu, a pop-up window opened where the user entered a name, then the user created the duplicate, and then the user was able to configure the remaining settings. This has been improved. The new workflow is as follows:

1. The user selects Duplicate from the context menu.
2. An edit page opens. The settings are prefilled from the selected object.
3. The user configures all of the settings as needed.
4. The new object is created upon saving.

This improvement relates to situations when a user has already selected one single entry from a drop-down list, and now the user wants to change that selected entry. In the past, the drop-down list looked like it only contained the one selected entry. Users needed to first deselect this entry before they saw the full list. This behavior was improved for a better user experience.

They now all follow the same design guidelines, use the same default window size, display elements in the same order, and allow users to resize the window with the cursor. These changes for consistency improve the user experience and make the application more intuitive.

• Assign product variants
• Add project members
• Project documents area > Right-click and select Add columns

• Upload window for test attachments (e.g. photos, videos, channels, etc.)
• Photo and video carousel
• Edit test window
• Apply template window while creating a new test
• Duplicate option within the context menu
• Import tests option within the context menu of the Projects and collections window
• Assign manually option within the Set as project status function
• The window that appears when opening add-on, e.g. the Report Designer add-on
• Move to another project option within the context menu

• Inspect code option within the calculation rules, presets and preset bricks
• Multi edit window for editing multiple MDM requirements or MDM test cases at once
• Change password window within a user account
• Access token window
• Manage categories button within the Test templates
• New value button within the MDM attribute value lists
• Duplicate MDM requirement window

• General confirmation windows, e.g. the confirmation windows that appear when deleting an object or when exiting a form with unsaved changes
• Session timeout window due to inactivity
• Loading dialogs
• Error Snackbar > Details
• PDF viewer

This impacts every GraphQL endpoint, and it will be a breaking change for requests which exceed the threshold.

To reduce the complexity, some good practices are:

• Split requests including a lot of data into smaller, faster requests.
• Load additional data asynchronously.
• Remove unnecessary data from requests.

The general logout endpoint /api/logout now only accepts POST requests and returns a JSON response. Client-side code is responsible for handling this response. The application frontend renders the JSON data on a new, consolidated page.

In the past, the test case remained in the application, but it did not appear in the project requirements grid due to missing requirements. That means, there were project test cases, which were neither visible nor could be deleted. This has been changed to prevent empty project test cases.

This change relates to the test details page in  Result. Users can now manually add an attribute that does not have a matching MDM attribute.

The application provides GraphQL and REST API endpoints. The REST API endpoints are deprecated and are now being removed. Any third-party implementations should use the GraphQL endpoints at api/graphql and remove any requests against the old REST endpoints.

This fix relates mainly to the requirements grid in  Project. In the past, when a user changed the grid view (e.g. added or removed columns), the column definitions were not always updated correctly. That means, e.g. the user saw columns that shouldn’t have been available, or the user saw outdated column definitions. This issue was fixed by adding a migration functionality to the user content, which saves client content on the server and synchronizes it between clients and sessions.

This fix relates to the views, which are available in several grids throughout the application e.g. in the project requirements grid, the MDM test case grid and the MDM requirements grid. In the past, users received an error message when renaming a view. This has been fixed.

This fix relates to the Documents area in  Project. Specifically, it relates to the attribute values, that can be added to documents. In the past, selected attribute values were only displayed for a short moment before they disappeared again. This behavior has been fixed.

This fix relates to the function for Comparing test cases and requirements with their MDM equivalents. In the past, the check boxes were not displayed in the row headings. This has been fixed. The check boxes are now available again.

This fix relates to the documents grid in  Project. In the past, if a user changed or added project document attributes, then the Created by information was updated to show the user who made the changed. This has been fixed. The Created by information is set on initial import and it is no longer changed due to any further modifications of the project document.

This fix relates to the process of creating or editing milestones in  Project. In the past, users received an error when clicking on the calendar icon ( ). This has been fixed. The date picker now works correctly again.

This fix relates to the documents grid in  Project. Specifically, it relates to global filter icon, which is displayed in the header. In the past, the global filter icon did not turn red when activated. It also did not clear the filters when clicked. These issues have been fixed.

When saving a preset brick which is used in multiple presets, the parallel validation of presets led to an error. The error was fixed by adjusting the validation so that it does not use any db connection.

This fix relates to the Attributes tab in  Result. In the past, the raw value was shown in the Value column. This has been fixed. The column now shows the display value.

This fix relates to the Show column definition context menu item in the  Result test grid. In the past, the column definition was only displayed for non-grouped columns. This has been fixed. The definition can now displayed for grouped columns as well.

This fix relates to the Edit tests window in  Result. Specifically, it relates to the filters that are available for each column header. In the past, these filters were not working. This has been fixed.

In the past, this context menu item was visible in all grids throughout the application. This has been fixed. It is now only displayed in the relevant grids.

The application header font was temporarily changed from white to black, which made the texts difficult to read. This change only affected a few, specific customer systems. It has been fixed.

This fix relates to the function for editing multiple MDM requirements at once. Specifically, it relates to situations when the user searches for MDM attribute values in the Context tab. In the past, only some of the values in the list were searchable. This behavior has been fixed.

This fix relates to the page for editing users, which can be accessed by navigating to   > Configuration > User management > Users. In the past, the selection trees for assigning the user to groups and global roles did not display any values if no checkbox was checked and a flat hierarchy was displayed. This has been fixed. The selection trees are no longer empty under these conditions.

This fix relates to the process of uploading files, e.g. project documents or MDM test case side panel attachments. In the past, the user did not see any feedback after uploading attachments. New files were only visible after refreshing the browser. This has been fixed.

This fix relates to the process of editing multiple MDM requirements or MDM test cases at once. In the past, numeric attributes were not correctly converted to SI units, leading to inconsistent behavior compared to single-item editing. This has been fixed. Numeric values selected in the multi-edit dialog are now converted to the correct SI unit before saving.