1.211

When viewing pool versions with filters, the pool versions are no longer sorted by the creation time. Rather, they are now sorted by the version number. This prevents rare cases when, due to different connection speeds for different clients, there might be pool versions whose version numbers are not in the same order as the creation time. Such pool versions were misleading.

App scripts can use links with folder paths from the jobs view again.

In some cases, some check boxes in the properties panel were shown as checked, even if in the background this was not the case. This behavior has been fixed.

In the past, after setting a pool version public, the history comment was still displayed in bold text in the Pool version area. This made the public pool version look like it was still private. The incorrect bold styling remained visible until the user interface was refreshed. This behavior has been fixed.

In the past, when two pool versions were compared in the Compare&Merge tab, then the drop-down menu in the Version column displayed an extra entry without any information. This has been fixed.

A run config can contain its own configuration file for the runner. This file will be merged on the runner server to form the full configuration for that particular model job. In some cases, the merge operation led to some corrupt parts of the configurations. This behavior has been fixed.

In the past, when two pool versions were compared in the Compare&Merge tab and the user clicked on Apply to create a merged version, then the new pool version was created but the Compare&Merge tab was wrongly left open by the client, leading to confusion on the user side. This behavior has been fixed. Now the tab automatically closes when the merged pool version has been created.

In case of components in live mode pool versions, it was not possible to upload check results for them to the server. This essentially meant that components could not be checked in live mode pool versions. This behavior has been fixed.

In case of run configs containing warnings and/or errors due to obsolete/deprecated/blocked entries or due to parameter conflicts, the assembly or the remote submit will fail with an error. A short description of this error is now shown as a message directly on the job in the jobs view.

In case of multiple selection, for example when selecting hundreds of run configs, the Properties tab ran into performance issues. Some of these issue were fixed, leading to a performance improvement for the Properties tab.