In the place for the line of JS you can put as much JS as you want but it gets messy to write and read. White space does not count between JS statements, and the semicolon is the JS statement separator.
It is better to merely put a call to a JS function in a JS module that you built and integrated into the guiDesigner file. The advantage is that the module and its contents can be built with a good JS editor that will also syntax check the code. You can pass arguments on the call if needed.
Look into tokens that can be associated with a join. The tokens may be easily used to hold auxiliary state/status information as they can be read/changed. You just need to do a lot of reading about JS in the CF Scripting documentation.
As a rule, you can do everything you want in JS. The reason many advanced developers chose CF was because of the integrated JS engine.
--
You received this message because you are subscribed to the Google Groups
"CommandFusion Software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to commandfusio...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--