1.265

Users can configure the synchronization settings under   > Settings > Connection Settings > Synchronization so that background synchronization only runs while users are inactive. Now, the unattended background sync will also automatically be paused when the user becomes active again.

There is now a platform validation mechanism that checks the operating system distribution and version when the application starts. This feature prevents deployment and runtime issues on unsupported platforms by detecting incompatibilities early in the startup process. If the platform is not supported, users see an error message with the unsupported platform details. The following platforms are supported:

• Ubuntu 20.04 LTS and later
• RHEL 8 and later
• CentOS 8 and later (CentOS 7 explicitly unsupported)

Note: A --ignore-platform-check command line option was also implemented as a way to bypass the check. However, this is not recommended and it requires a conscious decision by the user.

In the old component grid, if a component is locked in a live pool version, this is shown by a small purple padlock in the “Name” column. This lock status has now also been implemented in the new component grid.

In the past, another background sync could be started while one was already running or queued. This resulted in multiple simultaneous background syncs. Now, only one background sync runs at a time. If another sync is already active, then no additional sync will be started, and the sync interval will only begin counting after the previous sync has completed. Manually triggered syncs are not affected by this limit.

This improvement relates to situations when a user edits a run configuration in the Properties view. In the past, the run was deselected if the user changed an attribute that was used in the grouping structure in the Runs view. To continue editing the run, the user then had to locate the run again under its new grouping level. This has been improved. The selection is now preserved regardless of grouping changes made in the Properties view.

In the past, the auxiliary content loader request_run_parameters_list did not return results for run configurations whose parameters belonged to auxiliary attribute groups. This has been fixed.

In the past, the Show only component attributes option was shown in the parameter grid even though this grid does not contain any components. The option has been replaced with Show only assigned attributes.

This fix relates to history comment propagation. In the past, if a user emptied an existing comment, then the comment was no longer taken into consideration for automatic propagation. This has been fixed. After being cleared, the comment is again eligible for propagation when the user types a comment above or below it.

In the past, duplicate entries were created when copying and pasting a multi component between branches. That means, sub-components appeared twice: once as direct children of the target group and once inside the multi component. This has been fixed.

In the past, if a user started an external application, components with the data format “external applications” (key: external-app) were not written to the support directory. This has been fixed. Such components are now written to the support directory when they are connected to the external app script via dependencies.

In the past, when multiple mounted sub-pools were displayed in the import mask, users could only import files into one of them, even though all sub-pools appeared to be selectable. This has been fixed. Files can now be imported into any of the displayed mounted sub-pools.

This error occurred when a user edited a large file in an external editor, and then closed the editor and began typing a history comment. In the past, the page would reload mid-typing and reset the comment, forcing the user to start over. This has been fixed.

In the past, when a user selected multiple components and then removed more than one attribute from these components in the Properties view, previously removed attributes reappeared. For example, removing the second attribute caused the first to reappear. This has been fixed. Note: Removing a single attribute worked as expected.

This fix relates to history comment propagation. In the past, propagated history comments sometimes disappeared after clicking on Set public. This happened if there were changes to two different objects on the same level, e.g. changes to a parameter group and a component group. This has been fixed.

In the past, successfully entered history comments were displayed in bold and with a red cell outline. This was changed because the red outline was often perceived as an error indicator. Now, successfully entered or edited cells are no longer displayed with a border.

In the past, setting permission markers on a pool version could freeze the user interface. This has been fixed.