Difference in startup arguments in 2023.03.3 LST and 2023.09

[bodnarescu.diana]

Hello,

In 2023.03.3 LTS the startup arguments are in application.getStartupArguments()[1]

2023.03.3.LTS.png

In 2023.09.0, they are in application.getStartupArguments()[0]:

2023.09.0.png

I could not find this in the release notes, is this a lasting change?

Thank you,
Diana

[mboegem]

Hi Diana,

during ServoyCamp I've noticed the same.
Haven't had time to have a closer look as Johan tried the same and wasn't experiencing this.

I guess, to be continued...

[jcompagner]

are we talking here purely for getStartupArguments? what i also tested was the onsolutionopen(args)

that seems to be fine for me

[jcompagner]

i think i know why i didn't get this

i was testing with an "a" variable in the url

it oculd be that it is broken when you don't do that at all.. (so no "a" variable")

[bodnarescu.diana]

Thank you Marc, Johan,

Indeed if I add, in 2023.09.0, an empty "a" argument in the URL, i get the empty string in application.getStartupArguments()[0] and my other arguments in the application.getStartupArguments()[1]:

2029.09.0_with_empty_a.png

If I don't add it, my arguments are in application.getStartupArguments()[0] as seen in my initial post.

In 2023.03.3 LTS, if you don't add the "a" parameter in the URL, you get it anyway, as null, in application.getStartupArguments()[0], and the rest of your arguments you will get in application.getStartupArguments()[1].

I would like to know if this 2029.09.0 is a lasting change, or you will revert to the behavior of the 2023.03.3 LTS.

Many thanks,
Diana