Servoy 2023.3.1

[jcompagner]

We are pleased to announce the availability of Servoy 2023.3.1 (release number 3843)

This version is available through the the download site

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

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 2022.12 (4.26)

See whats new for the global changes

See the issues list for a complete overview of all the cases and fixes for the 2023.3.x releases.

Make sure you use all the latest webpackages that also have the 2023.03.x
Older versions won't work in combination with Servoy 2023.3

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

Also for various packages there are new releases, bootstrapcomponents, servoy-extra and nggrid.

Also ngdesktop and its plugins have new releases.

[steve1376656734]

Hi Johan,

The release notes show that this includes the fix for SVY-18164 but the support system shows this ticket as still in progess. Is this fix complete?

Thanks
Steve

[rafig]

Congrats Johan & Servoy team!

[Andrei Costescu]

@Steve. Yes, the fix for that issue is in the build.
It's still open in order to fix another similar problem - but that other problem will only make it in next build. I'll add a comment after that one is fixed as well.

[steve1376656734]

Hi Andrei,

Thanks for clarifying that. I was particularly interested in this ticket as I was directed to it by Paolo following a session he and I had together regarding one of our components whereby the emit() was not passing data back to the server. Should that be fixed by the current code or do we have to wait until the next release?

Thanks
Steve

[steve1376656734]

@andrei - I have run some tests and can confirm that the current code DOES fix our issue.

Thanks
Steve