Found a bug with the script variable checks. It seems it only works for about 500 lines.
For example if you declare a variable on line 10, then after line 510 , any lines that reference the variable think it has not been declared, and so throw an error.
I'm wondering if it's possible for scripts to give an indication of matching "Enter Find Mode" and "Perform Find" (or constrain/extend) script steps ?
While I realise this is not relevant for some developers who simply put their find criteria inside the "Perform Find" step, for myself and others it would be beneficial.
All finds I do in scripts are explicit, I enter find mode, do stuff, then it is followed by a "Perform find, "Constrain found set" or "extend found set" step somewhere else in the script. Never do we enter find mode and have the find happen in another script...
What would be useful is highlighting much like if statements and loop statements, where putting your mouse on either steps, highlights the corresponding.
Or better still error/warning if there aren't matching . We have had situations in older solutions where developers have forgot the "Enter find mode" step, and so inadvertently overwrote record data with find request data !
This is not a high priority request, but if it were a straightforward option to add much like If/Loop highlighting, or variable checking, that would be cool.
Well, I am not sure that we can do good checks.
I could of course extend the If/loop Highlighting to do the same for the "Enter Find Mode" and "Perform Find" pair.
But I assume there may be clients where they have one of these commands alone.
Completely understand that , it could be a toggle preference to use or not use this feature. I just know for the likes of our company we always use both in pair.