Servoy 2024.3.1

[jcompagner]

We are pleased to announce the availability of Servoy 2024.3.1 (release number 3944)

This release has the same blobloader fixes as the 2 LTS releases that are also released.
But it also has other security fixes, so it is very recommended to upgrade to this release if you are on a 2023.6 or higher (up to 24.3.0) to this release
See release notes for possible breaking stuff.

If you are on LTS release or any older version please upgrade to 2022.3.9 LTS or 2023.3.7 LTS

This version is available through the download site

An installation (coming from the normal installer or from a platform specific archive) is shipping with a Java VM (Java 21.0.1)

So for the platform specific archives you don't need to install or have java on your system.

This release can be updated by using the "latest" url: http://download.servoy.com/developer/latest/ (when you come from 2019.03 or higher)
This release is build on Eclipse 2023.12 (4.30)

See whats new and fixed issues

This is a release in our quarterly release cycle
if you want to stay on the LTS path you need to stick to 2023.03.7 LTS and enabled only the lts update site.

please also update the webpackages that also have releases for 2024.03

If coming from a much older release like 2022.03 then you first have to updated to 2023.03 and then go to 2023.12
This is because of an Eclipse update bug that prevents these updates.

[rafig]

Congratulations!

[robert.edelmann]

Thanks a log for the release, looking forward to try out great new things!

[steve1376656734]

The case list section of the release notes appears to be broken:

caseList.png

[sean]

Hi Steve,

This issue was fixed earlier today. Please refresh the page to clear any cached content and it should be fixed.

Best,
Sean

[jcompagner]

We will do a 24.3.2 release very shortly because of some conversion problem in nested json/map types that have a null value in one of the properties. This can/does affect nggrid and maybe some other big components that are using this kind of stuff.

But also some are now complaining that there are more scrollbars visible, this is because we reverted this case: https://servoy-cloud.atlassian.net/browse/SVY-15946
And that is the right thing todo, because we where way to relax to show a form in a tabpanel.. the form was show based on his last most bottom most component not the design time size of the form. So suddenly a button that had at design time still 40px below it would have 0px below it when it was shown in a tabpanel. (and if that size did fit no scrollbar would appear).
Now we set the min width and height for css positioned forms in tabpanels so they are really always the design size you say it should be. But this can result in suddenly scrollbars appearing because the design size is a bit bigger then what was in the browser calculated before.