An editor variable can be created by the user and included in any user defined expression where a built-in editor variable is also allowed. For example a custom editor variable may be necessary for configuring the command line of an external tool, the working directory of a custom validator, the command line of a custom XSLT engine, a custom FO processor, etc. All the custom editor variables are listed together with the built-in editor variables, for example when editing the working folder or the command line of a custom validator, the working directory, etc.
Creating a custom editor variable is very simple: just specify the name that will be used in user defined expressions, the value that will replace the variable name at runtime and a textual description for the user of that variable.
An editor variable can be created also from a Java system property. For example the Java system property var.name can be inserted in any expression where built-in editor variables like ${currentFileURL} are allowed: just type ${system(var.name)} in the field where you need that Java system property.
An editor variable can be created also from an environment variable of the operating system. For example the environment variable VAR_NAME can be inserted in any expression where built-in editor variables like ${currentFileURL} are allowed: just type ${env(VAR_NAME)} where you need the environment variable.
The current date can be inserted at cursor location with the custom variable ${date(yyyy-MM-dd)}. The date format is: the year with 4 digits, the month with 2 letters, the day with 2 letters.
The custom editor variables are configured in Preferences.