1.264

In the past, data was synchronized at fixed intervals (e.g., every 10 minutes) regardless of whether the user was active in the client. This could cause performance issues and interrupt workflows. A new inactivity-based option was added under   > Settings > Connection Settings > Synchronization. This option is called Required Inactivity for Scheduled Sync. It causes scheduled syncs to only run after the user has been inactive for a specified inactivity period.

Context menu actions for adding, removing, or converting multi-components can have consequences that are difficult to reverse. For example, clicking Convert combinations to multi components in the context menu of a pool version creates several multi-components in a step that cannot be reverted. To prevent accidental usage, these context menu entries can now be disabled via the feature switch --features not:multi-components.

This improvement affects several areas in the application, e.g. the Runs and Groups areas. By default, data is unsorted in these areas. To improve usability, sort icons were added to the headers so users can sort the data in alphabetical or reverse alphabetical order. The following icons are now visible:

•   Unsorted (default state).
•   Sorted in alphabetical order (A-Z).
•   Sorted in reverse alphabetical order (Z-A).

This fix applies to multi run configurations, which can be defined using discriminator attributes, parameter tables, or both. In the past, if a multi run configuration used only a parameter table (i.e. no discriminator attributes), the child runs were created correctly but each iterated parameter was incorrectly flagged as “ambiguous”. This has been fixed.