2019.1

document. Let's suppose execution is suspended before an if-statement: if (foo == 3). If foo
is not equal to 3, but you'd still like to see what would happen if it were, you could add the
expression foo = 3.
Expressions are evaluated automatically when execution is suspended.
l
The Add: button lets you add an expression to the overview. Expressions must be unique
and cannot be empty; empty expressions will be removed.
l
To edit an existing expression, just click the entry.
l
The Delete button removes the selected expression.
Step-through buttons
The buttons at the bottom of the Script Debugger let you step through the code. When you step
through the code it always steps relative to the most recent stack frame.
l
Into (F5): Step into the function on the current line, if possible. A common use case for
this is to step into a results.each() call. Note that you can only step into functions
that are defined in user scripts. For other statements this behaves like (Step) Over.
l
Over (F6): Step over the current line.
l
Return: Step out of the current function. This only works if execution is suspended inside
a function defined in one of the user scripts. Otherwise it behaves like (Step) Over.
l
Resume (F8): Continue up to the next breakpoint or until the output run is finished.
l
Restart: Start the debugging session over from the beginning. This button is only
available when the output run has finished. Execution will be suspended on the first line
of the output run, even if that line does not have a breakpoint.
l
Close: Close the Script Debugger.
Script wizards
Wizard types
Script wizards are simplified interfaces for common scripts in templates. These are the
available Script wizard types.
l
Text Script: This is the default script that is created when a data field is dragged from the
Data Model onto the page. See "Variable Data" on page322.
Page 474