1.252

Note: This feature relates to the new component grid, which is still being developed and which is deactivated by default. Currently, the new grid is only used if it is specifically activated with the command --feature new_component_grid while starting the client.

This feature relates to the rail graph within the pool version area. In the past, users could switch to an older view, where it was not possible to filter in the rail graph. This outdated view has now been removed entirely.

This improvement relates to the Changes area within the Properties view. The wording was changed for clarity. Users now see that the changes are with respect to the pool version.

When operating the primary and secondary service in parallel, it is necessary to avoid conflicts between components, pool-versions etc. on both services. To ensure this, it is now possible to configure the secondary service as write-through. That means, when updating items on the secondary service, the update is first forwarded to the primary service. This way, no conflicts can develop and the primary service always has the authoritative information.

In the past, some of the pages in the Admin panel (for example, users and permission groups) failed to load with a URL error. This has been fixed.

New public keys of client checkouts on the secondary service are now retained during sync against primary service. So that such keys can still be used later on.