2021.2

Parameter names appear as keys; default values appear as values.
2. Either browse to the location of a JSON file and select it, or paste/write/edit the JSON
directly in the box below the File field.
Note that JSON arrays are not supported.
3. Click OK. The keys of the JSON object appear in the Name column, the values in the
Value column.
4. For new parameters an attempt is made to derive the data type from the value, but this is
only possible to a limited extent. Double-click any new parameter to set its desired data
type.
Editing a runtime parameter
To edit a runtime parameter, either:
l Double-click the parameter; or right-click and choose Edit; or select the parameter and
click the Edit button ( ), and modify it in the Edit Parameter dialog.
l
Click the Set Values button ( ) and edit the JSON. Note that this method cannot be
used to change the name of a runtime parameter. You can only change the values and
add new runtime parameters this way.
If the Data Model contains a JSON Record Data List (see "A JSON Record Data List" on
page976), you could edit the runtime parameters by adding or editing the parameters object
using the "JSON sample data dialog" on page974.
Accessing runtime parameters
Runtime parameters in a template are accessible in scripts, via merge.template.parameters.
(See "Standard Script API" on page1283.)
The merge.template object has a parameters array that allows to access the template's runtime
parameters. (See: "template" on page1436.) The script can read and could also change the
values. Note however that any runtime parameter's value will be reset with each new record
that the template is being merged with.
Contexts
Contexts are parts of a template that are each used to generate a specific type of output:
Web,Email or Print.
Page 468