1.227

This feature relates to the Runs area. In the past, users could already group run configurations based mainly on their attribute values. Now, users can also manually select the run configurations that should be grouped together. The basic workflow is as follows:

1. Select one or more run configurations.
2. Right-click to access a context menu.
3. Select an option to group the run configurations into a so-called “collection”.
   • Add to collection: This option is available when you select runs, run groups or collections (e.g. it is possible to add entire groups/collections to another collection).
   • Remove from collection: This option is available when you select runs that are already included in a collection. The runs will be removed from the collection.
   • Delete collection: This option is available when you select a collection.

In the past, history comments were automatically filled in from the other comments. This behavior was fine for indirectly created new versions of objects or private versions of objects that already had a history comment. But this behavior was not optimal for newly created objects (e.g. a new version of a component after being edited).

Now, users are forced to write their own history comments for newly created objects. This ensures that users do not simply take over the existing history comment that was automatically filled in. Rather, users are required to provide a good history comment themselves.

This improvement relates to the parameter grid and to the component grid. It is now possible to sort by multiple columns in these grids. It is now also possible to sort ISO dates.

Background information: Many actions that would automatically lead to a new pool version are deactivated, e.g. changing attribute values on components or deleting/replacing components. Users have to manually derive a new pool version before they can perform such an action. This prevents users from accidentally deriving new pool versions.

For this same reason, the “Copy&Paste” action has now also been deactivated in parameter tables in public pool versions.

This fix relates to the components grid. In the past, if a user grouped the components by a column, then that column was automatically deactivated. That means, if a user clicked on the   icon in a column header and selected the option Group by [Column name], then the column disappeared from the grid. This behavior has been fixed.

In the past, when a component group or pool version was set public, the automatically propagated history comments were not applied, when they should have been propagated upward. For example, after publishing the group, the comment was still empty, even though a comment was shown in the Set public window. This behavior has been fixed.

In the past, an error occurred when exporting an lpack. The lpack export job no longer had a “job_type”. This behavior has been fixed.