Field variables reference fields from the active field catalog of a document. Therefore, the field name (i.e., the .Name property of the field definition) also serves as the variable name. For tabular fields, the field name would thus have the form {table name}.{column name} (see the syntax of the property FieldCatalog[].Field[].Name).

However, such a specification is only sufficient if, in the context of processing, it is clear which line of the table is being addressed. This would be the case when, for example, initialization macros are executed for a field catalog. For table fields, this is done successively across all lines. If there is no additional line specification, table field variables always refer to the fields of the line that is currently being processed.

If, on the other hand, fields of another row are to be explicitly referenced or if the current execution context does not refer to table rows, then specify the row number explicitly in the variable name. The syntax for this is {table name}[{row number}].{column name}. The row number count starts at 1.

Constants are primarily used to maintain certain configuration values in a central location. These configuration values are inserted into the configuration data at the relevant points by pure text replacement at program start. The syntax %constant name% is used for textual insertion.

Constants can also be used in macro expressions at runtime. The syntax @ConstantName is used for this. Constants are always defined syntactically as a string. Typed values must be specified in the syntax of a literal (constant value) (see Data Types, Variables, and Constants). Text values must be written in additional quotation marks, for example. If a constant value cannot be interpreted as a syntactically correct literal, the value is implicitly treated as a text value.

Document variables are fixed by name. These variables contain the system's metadata for the document that is currently being processed.

File variables are variables that can be used when processing a file attachment of a document. The use of file variables is limited to file macros and to some macro functions in configuration properties of output formats and output systems.

In certain contexts, additional variables are available that include the folder of a file. In particular, this applies to the use case where references to attachments yet to be added to the file system are to be evaluated. For file attachments that have already been added to a document, on the other hand, there is no longer any access to their original folder via a file variable.

System variables are fixed variables that contain general system information and environment information. The contents of the system variables partly overlap with that of the environment variables. However, in contrast to environment variables, the values of the system variables are determined and prepared internally in the program.

The date and the time are used to create dynamic file paths (e.g., for backup directories). The colon is not a valid character in folder and file names in Windows, as ist is otherwise used to separate the time components. Therefore, a different separator is used here.

All (Windows) environment variables of the system, the current process, and the user are available.

For individual configuration properties or macro functions, there might be additional internal variables that are restricted to the execution context of these elements. Variables such as these are listed in the description of the respective element.