0.51.0

Previously, add-ons operated with command-line arguments to deliver configuration details and contextual information. With the latest update, environment variables have been introduced to offer the same information, streamlining accessibility and maintenance.

As part of this enhancement, command-line arguments will be phased out over time. Please refer to the deprecation notice for guidance on migrating to the new environment variable setup.

There is a new experimental feature, which automatically scales workers for pending add-on tasks.

This feature relates to the MDM test cases, which are found under   > Configuration > MDM > Test cases. When adding a new MDM test case or editing an existing MDM test case, users can now select a discipline.

This feature relates to the Apply calculation rule function, which can be accessed by navigating to  Result and right-clicking on a test in the grid.

This feature relates to the milestones in  Project. When editing an existing milestone group, the header now contains a trash symbol. You can click on this trash symbol to delete the milestone group.

This feature relates to the requirements grid in  Project. When you right-click on a requirement in the grid, you now have the option to edit the project test case. That means, you can now edit the test case to be project-specific.

This feature relates to the Set as project status function, which can be accessed by navigating to  Result and right-clicking on a test in the grid. Here, it is now possible possible to assign tests manually. That means, to manually match the test with the appropriate test case.

This feature relates to the Set as project status function, which can be accessed by navigating to  Result and right-clicking on a test in the grid. When entering a test value here, the assessment cell automatically changes color to show how the value matches the requirement’s thresholds.

It is now possible to double-click on a cell in the Assessment column and choose a different color if you want to manually override the automatic assessment. Note: Manually selected assessments are represented with the symbol  .

This feature relates to the requirements grid in  Project. It is now possible to compare the current status of your requirements with the status at a previous date. For example, you can look at a specific requirement and see how its value changed from one milestone to the next. Further information in the manual.

This feature relates to the MDM test cases grid, which is found under   > Configuration > MDM > Test cases. This grid now includes a Source column, which indicates whether the test case is internal or external.

• Internal: Internal test cases were added to the overview manually. They can be edited further or deleted.
• External: External test cases were imported into the overview. They are read-only, meaning that they can neither be edited nor deleted.

Users may now subscribe to receive status updates for tasks, even if they are not the task owner. This allows users to stay informed about the progress of tasks initiated by their actions, such as downloading attachments via an add-on. Previously, users initiating these tasks would not receive updates, as the tasks were executed under the system user. With this update, users can opt in to receive timely status notifications for such tasks, enhancing their overall experience.

This feature relates to the grid components, e.g. the test grid in  Result and the requirements grid in  Project. In these grids, users can drag column headers to the upper left corner, thus grouping the data. In the past, if multiple columns were grouped and then an additional filter was applied, any expanded groups automatically collapsed. This behavior has been changed. Now the collapse/expand state remains as it is and is fully unrelated to the filter function.

This feature relates to the attributes tab in  Result. This tab now includes a Raw value column, which helps users debug situations where an attribute value has been converted and the result makes no sense. For example:

1. An attribute holds angle information, and its display unit was set to deg in MDM.
2. The expected SI base unit is rad accordingly. This is the expected input unit.
3. The value is converted from rad to deg so that it can be displayed within the grid and the attributes tab.
4. If those attributes are obtained from a backend system, i.e. a third-party system, and they are imported directly in deg instead of rad, then the conversion will produce nonsense values.
5. In such cases, the user can look at the Raw value column to see the database value without any conversion.

This improvement relates to the test grid in  Result. Specifically, it relates to the context menu, which is accessed by right-clicking on a test in the grid. The context menu has been improved in several ways, for example:

• Icons were added to each item in the context menu.
• The items were rearranged, so that they are now displayed in a more logical order.

This fix relates to the test grid in  Result. The test results are now displayed correctly after having been grouped by their column headers and also sorted in asending or descending order.

This improvement makes it easier to apply test templates while manually creating a new test record in  Result. Specifically, it is now easier for users to understand the override behavior of templates.

For example, if a user selects multiple templates, there is a chance that the templates will both include the same attribute, but with conflicting attribute values. One template might set the barrier overlap to 40% and another template might set the barrier overlap to 100%. This improvement has now made it easier for users to understand which value will be applied when manually creating a new test.

This improvement relates to the MDM requirements, which are found under   > Configuration > MDM > Requirements. If you select multiple MDM requirements and then right-click, a context menu appears. This context menu includes an option to delete all of the selected requirements at once. In the past, it was necessary to confirm the deletion of each MDM requirement separately. This behavior has been changed. Now you only need to confirm the deletion once. This confirmation applies to all of the selected MDM requirements.

Previously, roles and groups were always updated whenever a user logged in using OIDC/OAuth. This was also the case even if OIDC_GROUP_FIELD or OIDC_ROLE_FIELD was left blank, resulting in the removal of all roles and groups of the user.
This has now changed. Roles and groups will only be updated if the fields are configured.

This improvement relates to the project permissions, which are found under   > Configuration > User management > Project roles. The project permissions are now grouped by topic.

This improvement relates to the toolbar in  Project and  Result. The toolbar is located at the top of the user interface. The toolbar has been improved in several ways, for example:

• It is now possible to navigate directly between  Project and  Result.
• In  Result, the list of presets is no longer hidden within the burger menu  . It now has its own drop-down list directly in the toolbar.
• The burger menu   now displays the same entries for  Project and  Result.

MdmAttributeConfiguration was removed. Use RdTestTemplate instead.

Prior to this release, it was possible to deploy the application using multiple domains at the same time:

# Helm: values.yml
envConfig:
  routing:
    hostnames: ["example.com", "another-example.com"]

The support has been dropped and the usage of domains streamlined. It is now possible to use only one domain. The example above needs to be rewritten to:

# Helm: values.yml
envConfig:
  routing:
    hostname: "example.com"

This fix relates to the MDM test cases, which are found under   > Configuration > MDM > Test cases. The test cases are now displayed correctly after having been grouped by their column headers and also sorted in asending or descending order.

This fix relates to the Apply calculation rule function, which can be accessed by navigating to  Result and right-clicking on a test in the grid. It is now possible for users with the permission Can execute calculation rule to apply the calculation rule. Users no longer need to have superuser status.

This fix relates to the requirements grid in  Project.

This fix relates to the test grid in  Result. The tests are now displayed correctly after having been grouped by the date column.

This fix relates to the test grid in  Result. The tests are now displayed correctly after having been grouped by a number value.

It is not possible to delete an MDM requirement that is already included in a project. Users who try to do so will receive an error message. The text of this error message was improved, so that it now advises the user to set the MDM requirement as obsolete.

It can take 10-20 seconds for a preset or a preset brick to finish saving. The user now sees a loading indicator during this time, and the save button is disabled. This provides the user with feedback, indicating that the save process is still running. It also prevents the user from clicking on the save button multiple times.