Common Settings
Each script has certain parameters, but you can also define the following general settings when calling the script.
Description
You can specify here any comment or explanation that will help you to understand the script operation in the future.
If Condition
If you need to perform some action when certain conditions are met, then you can specify these conditions in this field instead of using the If Statement.
How to define the If Condition field
The If Condition field contains a logical expression in Gentee language. The current command will only be executed if this condition is true. Otherwise, the current command will be skipped.
1GetVarBool("check1") || *GetVar("value1") > 5 2GetVarBool ("check1")
If you want to check only variables for true/false in the condition, you can use a simplified notation. In this case, it is enough to specify only the variable names and logical operations &&(AND), ||(OR), !(NOT). For example, if you specify myvar, it means that this command will be executed if the variable myvar exists and is not equal to an empty string, "0" and "false". If you specify !myvar, then the command will be executed in the opposite case.
1check1 && isopen 2!myvar || todo || myvar2
Advanced Settings
Here you can additionally specify general settings for the commands to be run.
params
In the editor, you can only specify specific states for checkboxes and dropdown lists. There may be a situation where you want the value of a checkbox or drop-down list to be determined while the script is running. Open the script in the editor and look up the names of the corresponding parameters. After that specify the desired value in params. For example, if the name of the checkbox parameter is recursive and you want the checkbox to depend on the mycheck variable, specify
1params: 2 recursive: "#mycheck#"
In this case it doesn't matter what state of the checkbox is specified in the script parameters below.
log
By default, the script sets the logging level that is specified in its settings. You can change the logging level by specifying this parameter.
1log: disable
ref
For each command you can specify an identifier name. The script contains a stack of such names and you can use these names to get information about which part of the script is currently running. For example, identifier names are used when saving form data in the Pro version. If you show the same forms, but want to use different autocomplete form data, then specify for each form its own ref parameter.
1ref: form1