Global variables not working after latest Scriptcase update

[psyhocabinet]

Global variables not working after latest Scriptcase update

After the most recent Scriptcase update, my applications that use global variables in SQL stopped working properly. The variables are defined in the WHERE clause like this:

WHERE nrFisa = ‘[parfisa]’ AND idconsultatii = ‘[paridconsultatii]’

At first, Scriptcase prompted me to enter the values, but now it no longer asks for them. The query runs with empty values ('') instead, and no data is shown. Both variables are set as IN, with POST and GET checked.

I tried clearing cache, recompiling, and using sc_reset_global(), but the issue persists. Is anyone else experiencing this?

I sent a ticket to Scriptcase support, but I still haven’t received any response — and it’s been over a week now.

In the meantime, I can’t work on my applications, which is causing serious problems with my clients. I’ve purchased a lifetime license, so this situation is very frustrating.

Honestly, I’m considering switching to another framework, although it’s quite difficult at this point. I’ve even started learning Laravel, because this isn’t the first time Scriptcase has crashed or caused unexpected issues.

[maxi]

Are the variable set as optional ?

[psyhocabinet]

no they are not , only in both of them , but that start to be a problem on the last update, and i have talk with them they know already about this bug , but nothing yet

[maxi]

I have just opened a ticket with SC support.
Let’s see how long it take to fix it

[Muthaka1]

I don’t seem to have this problem

[rinolt]

It also happens to me that global variables have strange behaviors after the last update.
In development environment the request for variable population often does not appear.

[psyhocabinet]

i put this link here to can see it better https://youtu.be/OGnDuEuMb00

[maximnl]

I had a similar problem with a grid, the parameters passed to a grid were used in sql where, but only with a fresh clean cache. Then they become cached and always stay the same even i see that other parameters are passed to the grid via a link.

I had to recreate the grid application and after that it worked as expected.

[psyhocabinet]

You can see in the video i have recreated the grid but the problem still exist

[psyhocabinet]

did you have last update ? , try to set up in sql a where clause and run it to see what hapend

[bwalujo]

can you show what is set in global variables?

[tango.cl]

I have the same problem with global variables, I have version 9.12.005 (7)

[tango.cl]

Uploading: Captura de pantalla 2025-04-16 004345.png…

[psyhocabinet]

I I can confirm that this is a known bug in Scriptcase, which I reported almost 3 weeks ago. I’ve already submitted 6 separate tickets, but unfortunately, it seems this issue is not a priority for the support team.

I still hope it will be addressed soon, as it directly impacts the functionality of the projects I’m working on.

[alvagar]

This is a very serious problem… I hope the SCRIPTCASE team takes action on this matter.

[robydago]

Maybe completely unrelated to this specific issue, but since some versions ago the warning message when a global var is not defined has changed to a misleading: “Create connection”.
It seems to complain about a missing db connection and not a global var.

[Danilo_Lima]

@psyhocabinet,

You mentioned that you had already opened support tickets for the tool a few weeks ago.

Have you not received any feedback yet?

If possible, please give us a little more detail about it, because we have a case regarding global variables in the Grid application that was reported to be analyzed and later forwarded to the responsible team. However, from the description you detailed here in the topic, it is not working at any time, while the reported case concerns non-functioning after the second execution of the application.

We await your feedback so that we can proceed.

Best regards!