0.58.0

This feature relates to the Project members area in  Project. It is now possible to add entire groups of users to a project, e.g. external service providers, simulation department, etc. That means, you can assign roles such as project manager and project contributor to single users, or to an entire batch of users as a group.

• This feature relates to the requirements grid in  Project. Now, the Details section of the side panel includes a field called Assigned project test case. Note: A project requirement always has exactly one assigned project test case.
• This feature relates to the MDM requirements grid under   > Configuration > MDM > Requirements. There is a new section of the side panel, which is called Assigned test cases. Note: An MDM requirement can be assigned to multiple MDM test cases.

This feature relates to the requirements grid in  Project. Specifically, it relates to the side panel, which can be expanded by clicking on a requirement and then clicking on  . Now, the Details section of the side panel includes the field Attribute key.

Use-case: The attribute key is useful for attributes that include a wildcard (e.g. the placeholder ?). In such cases, the attribute key is used to specify which exact attribute the requirement applies to. Example: Imagine you have an attribute for the dummy and use a wildcard so that the attribute applies to dummies 1-6. The attribute key specifies which exact attribute the requirement applies to, e.g. dummy 2.

This feature relates to the MDM attributes, which are found under   > Configuration > MDM > Attributes. The overview now contains a column called Component name. This column displays the component that the attribute belongs to. Furthermore, users can now filter, group and sort the overview by component.

This feature relates to the MDM test cases, which are found under   > Configuration > MDM > Test cases. When creating a new test case or editing an existing test case, users now see an area called Attachments. Here, users can manage any relevant attachments for the test case. That means, users can upload new attachments, download existing attachments or delete existing attachments.

This feature relates to product variants in  Project. Now, when you assign product variants to test cases, the product variant’s name is automatically added to the end of the test case name. Use-case: If multiple instances of the same test case are added to the project, then this ensures that the test cases are clearly identified. Note: The variant’s name is always added to the test case name. This is not an optional setting. However, users can change the name any time via the context menu and edit form.

In the past, it was already possible to query the name and the planned date of the next milestone.

Users can now evaluate key test results on demand. That means, users can select one or more tests in the grid and then activate a color-coded evaluation of the key results. The color is provided by the matching project requirement’s thresholds.

This feature relates to the calculation rules, which are defined under   > Configuration > MDM > Calculation rules. Users can now right-click on a calculation rule in the overview and select Edit from the context menu. This opens an editing page, where users can modify the calculation rule.

This feature relates to the attribute value lists, which are found under   > Configuration > MDM > Attribute value lists. Users can mark attribute values as obsolete if they want to keep them for existing tests, but prevent them from being used again in the future.

In the past, users were able to select obsolete attribute values while editing attributes in the Edit tests window and while editing attributes in the Test details page. This behavior has been changed. Obsolete attribute values are no longer available for selection.

In the past, new workspaces were occasionally saved to the backend despite there already being a workspace available for the selected preset. This resulted in the number of workspaces accumulating and the performance decreasing. This behavior has been fixed.

There is now a profile information page under   > My profile. Here, users can see basic information about their own profile. For example, users can see which disciplines they belong to, e.g. crashworthiness, fatigue or pedestrian safety.

By using the DB aggregation instead of column functions, the time for calculating the aggregation can be reduced. The DB aggregation can be used by setting the function_name for value_aggregation_config to min or max. The parameter absolute needs to be set for using the absolute values.

On GraphQL preset query request “deprecatedContent” as subfield of field “parsedData”.

It is also possible to filter whether or not the attributes are assigned to any component.

This improvement relates to the window that is displayed when users add test cases to a project. When users press the save button ( ), it can take several seconds for the MDM test cases to be imported into the project. In the past, users did not receive any visual indication that the save process was still running. In some cases, this caused users to click on the save button multiple times and thus accidentally import the test cases multiple times. Now the save button is disabled during the save process and users see visual feedback that the process is still running.

This improvement relates to the pop-up window where users assign product variants to test cases. In the past, the pop-up window Assign product variants always opened after clicking on the save icon. This behavior has been changed. Now, the pop-up window only opens if the project includes product variants. If a project does not include any product variants, then the pop-up window does not appear.

This improvement relates to the test grid in  Result. The behavior and feature set are now similar to the usual table views using the Server Side Row Model backend implementation.

This improvement relates to the set state detail page. In the past, this page had a Requirement column, which displayed information in the form ‘RequirementName (TestResultIdentifier)’. In some cases, this was not enough information to clearly assign the test attribute. Now the Requirement, Test result identifier and Attribute key are all displayed in separate columns.

In the past, the test grid was empty if nothing was selected. The new behavior will help users assign tests to collections.

This improvement also fixes incorrect behavior in the grid when context column identifiers contain non-alphanumeric characters.

This improvement relates to the MDM requirements, which are found under   > Configuration > MDM > Requirements. Now when a user right-clicks on a requirement, the context menu only displays operations that the user is permitted to execute. That means, the context menu entries are only visible to users with the corresponding permissions.

This improvement relates to the MDM test cases, which are found under   > Configuration > MDM > Test cases. Now when a user right-clicks on a test case, the context menu only displays operations that the user is permitted to execute. That means, the context menu entries are only visible to users with the corresponding permissions.

This change relates to  Project. The field Project type has been removed from all areas where it was displayed, e.g. the project settings and the create new project dialog. The field was removed because it is not necessary as a separate type of information. Project attributes can be used to specify this information instead.

This fix relates to the requirements grid in  Project. In the past, when expanding several different grouping levels, the grid would sometimes reload unintentionally, causing all of the expanded groups to collapse again. This behavior has been fixed.

This fix relates to the requirements grid in  Project. In the past, no entries were displayed in the grid after applying a filter to the Test case column. This behavior has been fixed. The filter now returns the correct results.

This fix relates to the set as project status function in  Result. In the past, inactive project requirements were taken into account when setting the project status. This behavior has been fixed.

This fix relates to the preset bricks, which are found under   > Configuration > Result > Preset bricks. When creating a new preset brick or editing an existing preset brick, users can click on the Contact drop-down list and specify a contact person. In the past, the names in this list were displayed as Firstname (Lastname). This has been fixed. The names are now displayed as Firstname Lastname.

In the past, new workspaces were occasionally saved to the backend despite there already being a workspace available for the selected preset. This resulted in the number of workspaces accumulating and the performance decreasing. This behavior has been fixed.

This fix relates to the test grid in  Result. In the past, the grid did not display any tests if multiple column filters were used. For example, no tests were displayed when filtering for a specific date range and numerical value, even though matching tests existed. This behavior has been fixed.

This fix relates to the Report area within the test details page of  Result. In the past, the list of reports was displayed without any styling, i.e. the reports were displayed as plain text. This has been fixed. The list is now styled correctly.

This fix relates to the jobs list, which is found under   > Configuration > Jobs. It also relates to the user’s list of own jobs, which is found by clicking on   in the toolbar. In the past, clicking on the   symbol in the Artifacts column led to an empty page. This behavior has been fixed. Users can to download job artifacts again.

This fix relates to the jobs list, which is found under   > Configuration > Jobs. In the past, if a user scrolled through the list with the mouse wheel, then several entries in the list were skipped. This behavior has been fixed.

This fix relates to the MDM requirements under   > Configuration > MDM > Requirements. In the past, it was not possible to delete an attachment. No error message was displayed to the user. This behavior has been fixed. Users can now delete the attachments of MDM requirements as expected.