Upcoming

This feature relates to the requirements page in  Project. This page now has a header, which displays the currently selected status report. This helps users immediately recognize which status report they are working with.

This feature relates to the requirements page in  Project. The elements on the page were moved into separate panels, which can be closed and re-opened individually. This keeps the layout clean, and ensures that only the necessary information is visible. To hide or display a panel:

1. Click on the project in the toolbar.
2. Click on Workspace.
3. Click on the name of a panel to hide/display it.
4. Drag & drop the panels to arrange them as needed.
5. Click on Reset layout to return the page back to its original configuration.

By default, a maximum of 10 tests can be selected for an add-on in the Report tab. If a user selects more than 10 tests, then a warning is displayed and the user is asked to confirm whether they really want to proceed. It is now possible to adjust this limit for each add-on. This is done by adding the configuration variable MAX_TESTS_LIMIT to the .addon.yaml of an add-on:

settings:
  MAX_TESTS_LIMIT:
    description: ...

This feature relates to the life cycle permissions, which can be accessed by navigating to   > Configuration > MDM > Life cycles. Actions on tests in  Result are now scoped depending on the users’ life cycle state permissions, which are configured for each role.

This feature relates to the test grid in  Result. Most columns in the grid are defined with presets. However, tests also have some general information, such as the test’s name, owner and date when it was created. This information can now also be displayed in the test grid:

1. Click on   on the far right side of the grid.
2. Select the column General information ( ).

This feature relates to the list of available licenses, which can be accessed by navigating to   > Configuration > User management > License features. The list now includes a column Default, where you can see whether a license has been marked as default, i.e. whether it will automatically be assigned to all newly created users.

This feature relates to the life cycles, which can be accessed by navigating to   > Configuration > MDM > Life cycles. While editing a life cycle, users can now select the permission class “project” from a drop-down list. Doing so adds all of the existing project roles to the grid. In the grid, users then specify which permissions each project role should have in relation to each life cycle state.

This feature relates to the Comment and Description fields that are displayed in the side panel of MDM test cases. Users can now format these fields with Markdown syntax. For example, users can create clickable URLs and links, write lists, add lines of code and highlight text in bold or italic font.

This improvement relates to the My profile page, which can be found by navigating to   > My profile. This page now includes a Licenses section, which is accessible via the left navigation bar. Here the user can see which licenses they already have, and they can click on Change licenses to apply for additional licenses as needed.

License verification for the application can now be enabled via the helm value deployment.scale-license-server.enable. This is currently an experimental feature. To validate a license, the scale-license-server needs to be installed first.

This improvement relates to the status reports in  Project. Now when a user selects a status report, a loading indicator briefly appears over the project requirements grid. This indicates to the user that the status report is still loading.

This feature relates to the status reports, which can be selected in the  Project requirements area. Now when a user is working with a status report and reloads the page (e.g. because the user switches to a different page and then comes back), the status report is still selected. This improves the workflow because users no longer need to manually re-select the status report every time the page is reloaded.

• Activating a checkbox ( ) is not the same as selecting a row, i.e. the row is not highlighted in blue.
• If only one row is selected, i.e. highlighted in blue, then information about the test case will be displayed in the side panel. If more than one row is selected, then the message Select a single test case to see the detailed view will be displayed in the side panel.

In the past, both actions used the same permission. This created an incorrect coupling of responsibilities, making it impossible to allow a user to perform one of these actions without allowing him to also perform the other. This has been improved by separating the permissions. For example, now:

• Project Developers can add test case attachments as part of their daily project work.
• Project Managers / Admins can modify project requirements (e.g. thresholds, configuration) as part of their administrative tasks.

This improvement relates to the feature for comparing a project requirement with its MDM equivalent. Specifically, it relates to the way that thresholds are displayed here. To improve readability, the thresholds are now displayed in logical order, from lowest to highest value. Furthermore, the display unit is now displayed in dependence with the test result identifier.

This improvement relates to the process of duplicating a project requirement. In the past, the duplicated project requirement lost its link to the parent MDM requirement. This made it impossible e.g. to compare the project requirement with its MDM equivalent.

This improvement relates to the process of manually uploading test attachments, e.g. photos, videos and other files. In the past, the new files were not immediately visible after being uploaded. Users first needed to refresh the attachment grid. This has been improved. The grid now automatically refreshes, i.e. new files are now automatically displayed.

Previously, directly assigned user permissions were exposed via the user_permissions field, which relied on GraphQL’s connection-based pagination. This approach introduced unnecessary overhead and was not optimized for performance. We are introducing a new field, user_permissions_list, which returns all directly assigned user permissions as a simple list, improving query performance and simplifying access patterns. The field user_permissions should be considered deprecated and will be removed in the next major release.

This improvement relates to the process of changing a user’s password under   > Configuration > User management > Users. The workflow was improved as follows:

• The password can now only be changed by a superuser or by the user himself.
• If the user does not have a password yet (e.g. because the user account was just created), then the Current password field will no longer be visible when initially setting the password.

This improvement relates to users who use a PKI card (smartcard) for authentication. Specifically, it relates to situations when users pull out their card when leaving their desks and insert their card when returning again. Users are now redirected to the login screen if the OIDC token has expired.

This style of layout is no longer tied exclusively to the  Result dashboard. This change provides the technical foundation necessary for SCALE developers to begin implementing such layouts in other areas of the application, e.g. in the  Project requirements area.

This fix relates to situations when working with a draft status report and exporting a PDF status summary. In the past, the PDF summary did not list unmet requirements, e.g. yellow or red requirements. This has been fixed. The PDF summary now correctly lists all project requirements.

This fix relates to the process of creating a new project in the menu   > Configuration > Projects. In the past, while creating a new project, users received the following error message: Cannot read properties of undefined (reading 'name'). This has been fixed.

This fix relates to the process of adding MDM test cases to a project. In the past, users received an error when adding a large number of MDM test cases to an empty project. The job failed with a timeout after 60 seconds. This has been fixed.

This fix relates to the Add MDM test cases to project area. In the past, if a user selected one single test case and clicked on   to expand the side panel, only the Details area was displayed. This has been fixed. The areas Requirements, Context and Attachments are now also visible in the side panel again.

This fix relates to the Properties panel (previously the side panel) in  Project. In the past, Context information was displayed as one long list, rather than as easily readable chips. This has been fixed.

This fix relates to the Photos tab in  Result. Specifically, it relates to situations when the user has switched to the list view and created grouping levels. Such grouping levels are carried over when switching back to the icon view. In the past, the grouping levels disappeared when reloading the application. This has been fixed.

This fix relates to the Set as project status function. The “select all” checkbox was removed because it was unclear how this global selection should behave in case of non unique relation between test and test case.

This fix relates to the attachment grids in  Result. Specifically, it relates to situations when users group the data in the grid, e.g. by the description column. In the past, the attachment grid threw an error if some descriptions were null and other descriptions were an empty string. This has been fixed.

This fix relates to the Collections window in  Result. In the past, no action was performed when users clicked on the   button or when users right-clicked and selected   New from the context menu. This has been fixed. The buttons now work correctly again.

This fix relates to the preview function, which can be accessed by right-clicking on an image in the Photos tab and selecting   Preview from the context menu. In the past, nothing happened when clicking on the preview button. This has been fixed.

This fix relates to the Set as project status function. In the past, if a user clicked on Cancel, the entire screen would refresh and unnecessary API queries were triggered. This negatively impacted the performance and user experience. It has been fixed.

In the past, client state migrations were not executed for shared views in project requirements. This has been fixed.

This fix relates to the views, which allow users to save and share their grid configurations. Specifically, it relates to the search function ( ), which is helpful in situations when there are many different views, and users want to find a specific view. In the past, the search function was not working. This has been fixed.

This fix relates to the edit user page, which can be accessed by navigating to   > Configuration > User management > Users and creating a new user or editing an existing user. In the past, the Global roles section displayed both the global roles and the project roles. This has been fixed. The section now only displays the global roles.