Difference in load() with () and other functions

load():  Variables in here only evaluated once when the form first loads.  By "evaluated" we mean run the code that comes after the variable definition.  Since the code is only ever run once, it means we can save values in these local variables that won't immediately get overwritten.  So you're actually required to use load() to make a variable that can be saved to.

with():  Variables in here get reevaluated absolutely every time the user does anything with the form at all.  This allows for dynamic content, or things that refresh on a button click, for instance.  You don't even need to configure the button to really do anything.  It just causes the with variables to be reevaluated.  If you define an empty with() variable, it gets re-emptied every time the user clicks or types anything, so nothing can be saved there.

a!localVariables() fully replaces load and with.  The reason load and with aren't relics yet is because essentially every application ever uses only those.  But load() and with() are now essentially tech debt, but tech debt that EVERYONE still has, pretty much.

Each of your variables inside a!localVariables() should be defined with it's own a!refreshVariable function.  That function takes 2 parameters, where you define what the variable is, and define when that gets reevaluated.  Now you have not only the option of "never" and "any time the user does anything", but also things like "every 30 seconds" or "when this variable changes" or "when some other variable changes".  You should use this, because now you only have to make your with() variables update when it MATTERS whether they update or not.  But you can only do that by porting them over to a!localVariables and defining them with the proper a!refreshVariable.

load():  Variables in here only evaluated once when the form first loads.  By "evaluated" we mean run the code that comes after the variable definition.  Since the code is only ever run once, it means we can save values in these local variables that won't immediately get overwritten.  So you're actually required to use load() to make a variable that can be saved to.

with():  Variables in here get reevaluated absolutely every time the user does anything with the form at all.  This allows for dynamic content, or things that refresh on a button click, for instance.  You don't even need to configure the button to really do anything.  It just causes the with variables to be reevaluated.  If you define an empty with() variable, it gets re-emptied every time the user clicks or types anything, so nothing can be saved there.

a!localVariables() fully replaces load and with.  The reason load and with aren't relics yet is because essentially every application ever uses only those.  But load() and with() are now essentially tech debt, but tech debt that EVERYONE still has, pretty much.

Each of your variables inside a!localVariables() should be defined with it's own a!refreshVariable function.  That function takes 2 parameters, where you define what the variable is, and define when that gets reevaluated.  Now you have not only the option of "never" and "any time the user does anything", but also things like "every 30 seconds" or "when this variable changes" or "when some other variable changes".  You should use this, because now you only have to make your with() variables update when it MATTERS whether they update or not.  But you can only do that by porting them over to a!localVariables and defining them with the proper a!refreshVariable.

Unknown said:

Each of your variables inside a!localVariables() should be defined with it's own a!refreshVariable function.

I would differ on this point.  Local variables can also be defined simply with the value instead of the a!refreshVariable function, as long as the default functionality of a refresh variable is fine.  This includes refreshing on referenced variable change, NOT refreshing always, and not doing any of the more advanced refreshes.  I'd estimate that for maybe 80 - 90% of your average local variable use cases, this default setting will either be OK or will just make no difference, and for the remaining ones, you'd use a!refreshVariable().

Nice catch!

It is really nice that they made the default so useful.  Now you can easily do things like run a queryEntity with a different parameter but only when the parameter actually changes.

And I suppose if it doesn't reference any other variables, it's just a load() at that point, right?

Exactly - I really enjoy how much more easy and/or flexible things are now.

And yes, if it doesn't reference other variables, then it's essentially a load() value.