1.1.0

This feature relates to the requirements grid in  Project. Specifically, it relates to the PDF summary, which can be accessed by selecting requirements in the grid, right-clicking and selecting the option  Export summary from the context menu. An additional column called Test case was added to the report. This column displays the name of the corresponding project test case. The column provides more context in situations when the requirement name alone is not sufficient.

The project list can be accessed by navigating to   > Configuration > Projects. Here, admin users can see an overview of all projects directly within the configuration area. That means, they no longer need to navigate to  Project. to see a list of all projects. The list can be filtered, sorted and grouped as needed.

This feature relates to the test details page, which can be accessed by right-clicking on a test in  Result and selecting  Open details page from the context menu.

• The General information panel now includes a field called Owner. This field indicates who is responsible for the test. Here you see the owner’s user name and e-mail address (if available), as saved under   > Configuration > User management > Users.
• It is possible to change the test’s owner, i.e. to transfer ownership to a different user. To do so, click on the  Edit button in the upper right corner and select a different user from the Owner drop-down list.

This feature relates to the add-ons, which can be found by navigating to   > Add-ons. Specifically, it relates to the add-on’s history, which can be found by right-clicking on the add-on, selecting  Details from the context menu, and expanding the History area. Users can now click on the button   to revert the add-on back to a previous version. This helps developers, e.g. easily switch between different versions (test vs. production) while developing the add-on or in case of bugs.

This improvement relates to the grids in SCALE.sdm. Users can now press the keyboard arrow keys to switch between lines and columns in the grid. This allows users to navigate more quickly.

• The up/down arrow buttons switch between lines in the grid.
• The right/left arrow buttons switch between columns in the grid.
• Press shift + arrow button to select multiple lines or columns.
• Use the mouse to select specific cells in the grid.

File uploads were previously handled by the application service directly, blocking resources on slow uploads and limiting the processing time for large files to a maximum of 60 seconds.

A new service called Phex was introduced, which acts as an MITM proxy and intercepts all file uploads. It handles and prepares them prior to forwarding the request to the application. This saves resources and reduces the time it takes to finalize the file upload.

If using custom container registries, make sure to synchronize the new container phex.

This feature relates to the permissions that are necessary for viewing the jobs of all users under   > Configuration > Jobs. In the past, users who were marked as staff were automatically able to view all tasks. This has been changed. Users now need the permission Can view all tasks in order to view the jobs of all users.

Background information: This change was made because the “staff” role also includes other permissions, i.e. the ability to access the admin area under   > Admin area. There are cases when users, e.g. supporters, should be able to view all tasks, but they should not be able to access the admin area.

The mutation addMdmTestCasesToRequirementMutation was added, similar to the existing addMdmRequirementsToMdmTestCase mutation.

This improvement relates to the attributes tab in  Result. The following changes were made to the layout:

• The following buttons were added next to the quick filter (from left to right):
  • Clear all filters: Resets all column filters and the quick filter.
  • Autosize: The columns in the grid are adjusted to fit the content.
  • Reset: Resets the filtering, sorting, column order and grouping to the default values.
• The tabs Columns, Filters and Views were added to the sidebar on the right side of the screen.

This improvement relates to the context menu, which appears when right-clicking on a test or simulation in the  Result test grid. In the past, the Add-ons entry was grayed out and took quite a while until it was enabled. This has been improved. The context menu entry now loads more quickly.

This improvement relates to the following pages:

•   > Configuration > Preset > Presets
•   > Configuration > Preset > Preset bricks

In the past, users could click on a preset (or preset brick) in the overview and then click on   to expand a side panel, displaying read-only information. The side panel was removed, since it displayed the same information as in the grid.

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

• The Product variants area in  Project
• The Requirements area in  Project
• The Project members area in  Project
• The Select collections area in  Result
• The Jobs area, which can be accessed by clicking on   in the toolbar
• The Jobs area, which can be accessed by navigating to   > Configuration > Jobs

The context menus were compared and modified for consistency as needed. That means, e.g. they now all use the same wording, icons and order of entries. This improves the user experience and makes the application more intuitive.

This improvement relates to the configuration area, which can be accessed by navigating to   > Configuration. The configuration area has a vertical navigation bar on the left, which you can use to access various menus within the configuration area. The menu entries were rearranged in this vertical navigation bar. They now follow a more logical structure (see the comparison below).

Depending on the SCALE.sdm theming, hyperlinks were displayed too prominently. This has been improved. Links are now styled globally, i.e. the style definitions go into the global theming file. Hyperlinks now use the primary color and are underlined.

This fix relates to the requirements grid in  Project. In the past, if the grid was grouped by a column which had null/none values, then it was not possible to expand the row. This has been fixed.

This fix relates to the requirements grid in  Project. In the past, sometimes when users clicked on edit mode, a different view was applied. That means, the grid configuration changed, e.g. and displayed different grouping levels. This behavior has been fixed. The view no longer changes when using edit mode.

This fix relates to the page for editing status report templates, which can be accessed by navigating to   > Configuration > Templates > Status report templates, right-clicking on a line in the grid and selecting Edit from the context menu. In the past, after saving the changes, the application navigated to an invalid URL. This navigation URL has been corrected.

This fix relates to the Set as project status function in  Result. Specifically, it results to the Select status target pop-up window. In the past, the Base report drop-down list sometimes displayed private status reports. This behavior has been fixed. The drop-down list now only displays public status reports.

This fix relates to the calculation rules in  Result. Specifically, it relates to the Status column, which informs users how many calculation rules potentially match the test, and how many calculation rules will be applied upon saving. In the past, this column did not display any information. Instead, it displayed a progress bar, which continued loading endlessly. This has been fixed.

This fix relates to the calculation rules in  Result. Specifically, it relates to the   button, which is displayed on the far right side of the screen. Users can click on this button to access further information that is helpful for debugging. In the past, this button was missing from the screen. This has been fixed.

This fix relates to the Channels tab in  Result. In the past, the tab did not load correctly when there were inf values (the tab displayed “ERR”). This behavior has been fixed. The value inf is now accepted.

This fix relates to the test grid in  Result. Specifically, it relates to situations when the tests are grouped by a column with a display unit, e.g. the column Vehicle speed [km/h]. In the past, the grouping levels showed the raw value (e.g. 12.5 m/s) instead of the formatted value and display unit (e.g. 45 km/h). This 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 situations when the requirements have been grouped by test case. In the past, when users right-clicked on an external test case, none of the context menu entries were disabled. This behavior has been fixed. External test cases are read-only, meaning that they can not be edited, deleted, duplicated, or activated/deactivated. These context menu entries have been disabled accordingly.

Methods from DirtyModelMixin are used to calculate changes between different states of the objects. When a field was deferred, states were saved incorrectly and caused wrong calculation of the changes. This is now fixed by handling deferred fields.

This fix relates to the Staff and Superuser checkboxes, which can be found by navigating to   > Configuration > User management > Users and looking at the General information area. In the past, these checkboxes were available to all users (even users without permission to edit them). If a user without the necessary permission tried to edit the staff or superuser role, then a permission error occurred. To avoid confusion, these checkboxes are now only available to users with the necessary superuser permissions.

This fix relates to the permissions for status report templates. In the past, two different permissions were both named Can add status report template. This has been fixed. The permission for adding a status report template to a project was renamed Can add status report template to project.

This fix relates to the pages for editing user accounts, groups and roles. In the past, the save button did not become active when selecting different permissions in the permission tree. That means, the save button remained grayed out. This behavior has been fixed. The save button is now correctly enabled when permissions are changed.

This fix relates to various edit pages throughout the system. In the past, the save button was already enabled when the page was initially loaded, i.e. before any changes were made. This behavior has been fixed. The save button now remains disabled until the user makes a change.

This fix relates to the user groups, which can be accessed by navigating to   > Configuration > User management > Groups. In the past, the edit page did not open when right-clicking on a user group and selecting  Edit from the context menu. Instead, the page for creating a new user group opened. This behavior has been fixed. The  Edit context menu entry now correctly opens the edit page.