Script Parameters on Timed Triggers
Operating system version
Description of the issue
I'm not sure whether this is a bug or "expected" behavior...though it was definitely not expected among a few other developers I asked.
I am trying to start a timed script trigger using as its script parameter a variable defined earlier in the script.
I was puzzled and surprised by the fact that the variable in the parameter is not evaluated at the time the timed trigger is defined, but is rather evaluated at the time the triggered script actually runs.
For this reason, local variables won't work -- you have to use global variables (or else fields are static num/text). Isn't that strange?