Thanks for the suggestion! I understand that sc_select_where(add) can dynamically insert the WHERE condition at runtime. I’ll try this workaround to bypass Scriptcase’s issue with global variable prompts not appearing after the first run.
Still, this shouldn’t be necessary — global variable handling worked fine before the update. But I’ll test it and get back with results.
"Still, this shouldn’t be necessary " . you are right but i think the major goal is to have the application run fine. Also you could try to place in scripipinit something like: [glob_var]=[glob_var];
Sometimes you work around the problem. [glob_var]=[glob_var] is sometimes a solution. Sometimes globals get lost in situations where you need a blank to fix the issue. I have a similar issue open for quite some time where a global in an application link is passed, but not picked up by the linked application. Looks pretty similar to this problem. But if you use a blank, you will notice that the variable is sent.
The update version 9.12.007 (15) came out, where it says that there is an arrangement of global variables, I updated but I still have the same problem. The same error.
the same problem i have too , and i already write a ticket
Hello SC colleagues, has anyone been able to correct the problem with global variables? Two updates have been released and the problem has not been resolved.
I’m having serious SC globals issues as well.
Just installed version 9.12.009 hoping to fix them, but nada.
SC Team: What’s up with this issue? It’s been a long time, and I see nothing has been resolved.
not 100% sure yet, but i just disabled the notification module in the responsive menu app and it seems that session vars in all other apps are stable now.
it seems rather odd.
maybe any change\regeneration of the menu app would have had the same result.
i have no time to do any more test now; since the notification module was on but not actually used, I’ll leave it off for now.