1.237

This feature relates to the Properties view after multiple objects have been selected. Users can now click on a button (filter icon with red dot) to only show those groups that contain differences. This helps users easily identify changes, especially for objects with many groups and lots of information.

This feature relates to the BLOB retention rules that are saved under Admin > Model > Blob Retention. Specifically, it relates to the filter restrict-team-status, which restricts a retention rule to objects with a defined team status (accepted values are private, public and live). In the past, this restriction could only be set for the rule retain-individual-object-contents. This has been changed. It is now available for the other rules as well, e.g. for:

• retain-pool-version-contents
• retain-pool-versions-with-assembled-runs
• retain-marked-contents

Example use-case: Imagine you have three different pool versions - PV1, PV2 and PV3. You want to tag PV2 as the reference version. By creating a so-called “exclusive” tag, you can make sure that only one pool version is tagged as the reference version. If you set the tag for a different pool version, e.g. if you want to set PV3 as the new reference version, then the tag will automatically be removed from the old reference version, since the tag is guaranteed to be unique.

The following changes were implemented:

• The menu Admin > Model > Tags now includes a new column called Type. Here, users can select the type of tag (simple tag or exclusive tag). The tag type can not be changed later. Further information about configuring tags.
• Exclusive tags can only be used for pools/trees. When setting the tag for a new pool version, users see a message, informing them that the tag will be removed from other versions. This message also indicates the version from which the tag will be removed. Further information about adding/removing tags.

In the past, the client sometimes reacted quite slowly when switching between pool versions. It took a long time for the context (groups, runs, grid) to load. The performance has been improved.

• The button has been renamed for clarity. It is now called Reload because it reloads content from the server and displays any new content that was added server-side.
• If users have any unsaved changes, then when they click on this button, they will see a warning message, which informs them that their local changes will be lost.

This fix relates to situations when users copy & paste a pool version. Upon pasting, a new tab called Paste into [Pool and version number] opens. In the past, users were required to enter new history comments for some of the groups in this tab, before they could complete the paste action. This behavior has been fixed. The history comments for groups are now also copied & pasted, meaning that users are no longer required to enter new comments.

In the past, when copying a multi-run configuration with an explicitly referenced parameter table from one pool to another pool (with the same pool config and the same parameter tables), the copied multi-run configuration in the target pool was not able to find its referenced parameter table. This has been fixed.