2019.1

mouse to display a tooltip indicating in which sections the scripts has run (and in which
contexts).
l
Elapsed: Displays the total elapsed time since the start of the session. The table entries
are initially sorted based on the values in this column, from high to low. Hovering the
mouse over it will display a tooltip that indicates the breakdown of the execution time
across different execution stages.
l
Delta: Displays the estimated difference in performance between the current session and
the previous session. Uses average values, so should still work if the previous session
was stopped after a different number of iterations. Will be empty if no previous data is
available. Hover with your mouse to display a tooltip indicating the breakdown of the
execution time across different execution stages.
Script Debugger
The Script Debugger allows you to test personalization scripts by setting breakpoints and
stepping through the scripts. (See also: "Testing scripts" on page369.)
There are two ways to start the Script Debugger:
l
Click the Debug Scripts button in the toolbar of the Scripts pane. The Script Debugger
will pause and accept input as soon as it processes the first script.
l
Right-click an enabled script in the Scripts panel and choose Debug from the contextual
menu. The Script Debugger will pause and accept input as soon as it processes the
selected script.
The Debugger simulates an output run with only the current record and appears as soon as the
merge engine processes the selected script, or the first script if no script was selected. You can
then add breakpoints and/or step through the code.
Meanwhile, the Workspace will display the partially merged document.
Scripts and call stack
The left side of the window displays a list of all enabled scripts that apply to the current context,
in the order in which they are expected to be processed.
If the selector of a standard script or post pagination script has no matches in the current
resource (Master Page or section) the script will be skipped.
If an error is thrown, the rest of the current script is skipped and execution continues with the
next script.
Page 472