2021.1

Using variables and properties in an SQL query
When you use variables and properties in an SQL query, the selection will be dynamically
adjusted each time the data mapping configuration is actually used in a Workflow process.
To create a dynamic SQL query:
l The query must start with =
l Any variable or property must be enclosed in curly brackets: { ... }. This effectively inserts
a JavaScript statement in the query. Note that all other curly brackets must be escaped
with a backslash.
Inside the brackets you may enter any of the following property fields defined in the
Preprocessor step (see "Fixed automation properties" on page341 and "Properties" on
page343):
l Fixed automation properties. These are retrieved via the automation object (see
"Objects" on page393), for exampleautomation.jobInfo.JobInfo9 or
automation.properties.OriginalFilename.
l Properties that have their scope set to "Entire data". These are retrieved via the data
object (see "data" on page400), for example:data.properties.myProperty.
l Properties that have their scope set to "Automation variable". These are retrieved via
automation.variables(see "Objects" on page393), for example
automation.variables.FieldList.
Properties that have their scope set to "Each record" and can not be used because the SQL
query is executed before any record is created. For the same reason, variables declared in
other Steps can not be used.
Example
= SELECT {automation.variables.FieldList} FROM {automation.jobInfo.JobInfo9}
If the Workflow variable defined as FieldList contains the value "id,name" and Job Info 9
contains the value "MyTable", then this custom query, once parsed, yields the following SQL
statement:
SELECT id,name FROM MyTable
which is then executed.
Page 338