0.53.0

This feature relates to the list of starred projects in  Project. When you right-click on a starred project, you now have the option to open it in a new tab.

This feature relates to the Apply calculation rule function in  Result. Specifically, the sidebar now contains a Calculate again button, which is active if input values have been changed. This button updates the main grid with the new result.

This feature relates to menus that have a sidebar on the right side of the screen, e.g. the requirements grid in  Project. Click on   to open the sidebar. The sidebar can now be resized. That means, users can drag the border of the sidebar and adjust the width to meet their needs.

This feature relates to all of the grids that use the view feature, e.g. the test grid, MDM requirement grid and project requirement grid. Once users have configured a view, they can click on   and select the option Share. A new window opens where they can select a discipline and then share their view with all users of that discipline.

This feature relates to the Apply calculation rule function in  Result. Specifically, if a calculation rule fails, then users can now see information about the error in the sidebar. This helps users understand what went wrong and where in the code the error occurred.

This feature relates to the Set as project status function in  Result. Users can now open the Debug view, for example, if the list of matching test cases:

• Contains a test case that was not expected. The user wants to know why it matched.
• Does not contain a test case that was expected. The user wants to know why it didn’t match.
• Contains all of the correct test cases. However, some of the requirements in the test case fall under the unassigned category. The user wants to know why.

The debug view displays all of the attributes as a table. The attributes are sorted into their context groups. Here you can see the name of each attribute, along with its condition and test value. Finally, you can see whether or not the condition and test value matched.

This feature relates to the Apply calculation rule function in  Result. Specifically, the sidebar now contains an Arg column, which lists the input attributes in numerical order. This column helps you see which input attribute corresponds to which argument in your Python code.

This improvement relates to the Job detail view, which can be accessed by clicking on   in the toolbar or by navigating to   > Configuration > Jobs. Click on a job in the overview to access the detail view. The page has been redesigned so that the information is now easier to read.

This improvement relates to the MDM requirements side panel, which can be accessed by navigating to   > Configuration > MDM > Requirements. Click on a requirement in the overview and then click on   to expand the side panel. The History area has been redesigned.

This improvement relates to the Jobs area, which can be accessed by clicking on   in the toolbar or by navigating to   > Configuration > Jobs. The task 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 background color that is displayed e.g. in dashboard panels. Sometimes the panels used slightly different shades of white as the background color. This has been improved. The background color is now consistant across panels and gaps.

This improvement relates to the Job task log, which can be accessed by clicking on   in the toolbar or by navigating to   > Configuration > Jobs. Click on a job in the overview to access the task log. Angular CDK Virtual Scroll has been implemented to improve the performance.

This improvement relates to the function for adding MDM test cases to a project, which can be accessed by opening  Project, clicking on Requirements in the left sidebar and then clicking on Add in the upper right corner. In the past, a timeout error was displayed if you selected a large number of test cases and clicked on the save button. This behavior has been fixed. It is now possible to add even a large number of test cases.

This improvement relates to the requirements grid in  Project. In version 0.51.0, the response time became significantly slower when opening a requirement group. The response time has now been improved.

This improvement relates to all pages that have a button for creating or adding new items. On some pages, this was a “New” or “Add” button in the page header. For example, on the pages for MDM attributes, MDM requirements and MDM test cases. On other pages, this was a round plus button in the lower right corner of the screen. For example, in the attributes, photos and videos sections of the test details. For consistency, this button has been moved to the page header.

This improvement relates to the user edit page, which can be accessed by navigating to   > Configuration > User management and then opening a user account. There is now a chip next to the user name, which indicates whether the user is internal or external.

• Internal: Information such as the user name, e-mail and display name can be edited. If the user name is changed, then the user will need to log in again, as the current credentials are no longer valid.
• External: The user and the respective information came from an external identity provider. Therefore, information such as the user name, e-mail and display name can not be edited.

Changes to MDM requirements are now fully recorded in the History panel within the sidebar. The previously used AuditLog to display changes had been disabled. Existing information is not currently displayed in the frontend. However, this information is still saved and it will be migrated eventually.

RemoteTaskJob was used to run arbitrary tasks on the asynchronous workers when the task interface was initially released. Any tasks now have a specific implementation and the RemoteTaskJob no longer serves any purpose.

This fix relates to the requirements grid in  Project. In the past, some elements were displayed without considering the user’s permissions. This behavior has been fixed. Now users will only see those elements that they have permissions for.

This fix relates to the requirements grid in  Project. In the past, the names of context attributes were not displayed in the Columns side panel ( ). The names were also not displayed in the grid header. This behavior has been fixed.

This fix relates to the requirements grid in  Project. In the past, if you grouped requirements by a column header, and then you clicked on the Group column, i.e. you sorted the column in ascending or descending order, then it was not possible to expand a group and see its contents. Expanding a group led to an error message. This behavior has been fixed. It is now possible to expand groups while also sorting by the Group column.

This fix relates to the Set as project status function in  Result. In the past, this function did not correctly handle statuses with value lists. For example, statuses with the threshold values “Yes” and “No,” rather than numerical threshold values. In the past, the assessment was not displayed in the set state dialog. The written value was also not correctly shown in the  Project requirements grid. This behavior has been fixed.

This fix relates to the task list. Specifically, it relates to tasks that ran via runner. In the past, failed tasks were incorrectly given the status canceled instead of failed. This behavior has been fixed.

This feature relates to the Apply calculation rule in  Result. Specifically, it relates to the context debugging function. In the past, attributes with wildcard condition identifiers were displayed with the information None (Attribute not set). This behavior has been fixed. Now the actual values of attributes with wildcard condition identifiers are displayed.