About the Trace View
The Trace view appears in the Process Debug perspective. Use the Trace view to control your navigation through steps, and to see the progress of those steps, including errors, while debugging a process. The Trace view displays details of each step in a debugging session, and contains a toolbar you use to control the session in the active process editor tab. Click a row in the Trace view to inspect the corresponding pipeline data output in the Pipeline Data view.
The Trace view has a toolbar you can use to perform actions on the process as you debug it. The Trace view is the active view when you start debugging, providing immediate access to keyboard shortcuts. The following buttons are available, and available shortcut keys are noted:
The table below lists and describes the buttons.
Button | Description |
 Run / Resume F8 | Run the process from the current step to the next enabled breakpoint or to the end of the process if no breakpoints are enabled. Parallel tracks run simultaneously. Non-parallel tracks run sequentially. When you click Run/Resume, all tracks run. The selected eligible step does not affect this. |
 Cancel Debug | Cancel all processes associated with the current Process Debug session. This action is reflected in the Trace view. Canceling stops all steps in the parent process and any child or descendant processes. Process debugging step status symbols remain displayed in the process editor. |
 Clear | Clear the Trace view and remove all Process Debug status symbols from the process editor. |
 Step In F5 | Enter a call activity or subprocess. When you click Step In on a step that does not support stepping in, the process debugger steps over instead. Important:
The button action applies to the default step, which is outlined in the process editor. The menu beside the button allows you to step into an eligible step other than the default. |
 Step Over F6 | Run the step. If the step is a subprocess or call activity, run all the steps in it to the next enabled breakpoint or to the end of the subprocess or call activity if no breakpoints are enabled. When you step over a child process (of a call activity step) in the course of debugging its parent process, and the child process contains an enabled breakpoint, the process debugger opens the child process in a new process editor tab and stops at the breakpoint. The Trace view and the process editor reflect the current step status. Important:
The button action applies to the default step, which is outlined in the process editor. The menu beside the button allows you to step over an eligible step other than the default. |
 Step Out F4 | Exit from a step inside a call activity or subprocess. When you click Step Out from a step that does not support stepping out, the process debugger runs the process to the next enabled breakpoint, or to the end if no breakpoints are enabled. Important:
The button action applies to the default step, which is outlined in the process editor. The menu beside the button allows you to step out of an eligible step other than the default. |
Below the toolbar, the Trace view shows a table that contains the following information about the steps in the process being debugged. You can click column headings to change the sort order of the steps.
The table below lists and describes the steps.
Column | Description |
 Status Indicator |  Green square = step or process completed.  Yellow triangle = step or process completed with warnings.  Red circle = step or process completed with errors OR process canceled. |
Step | Step Label. |
Step ID | Step ID. |
Step Iteration | Number of step iterations. Represents the loop count for transition (sequence flow) and for webMethods Subprocess (Deprecated) steps. |
Loop Iteration | Number of loop iterations. Represents standard loop count for all Call Activity steps and BPMN Subprocess steps. |
Start Time | Step start time, and process start time when debugging starts. The time format is governed by your operating system settings. |
End Time | Step end time, and process end time when debugging has completed. The time format is governed by your operating system settings. |
Duration | Step duration time, and process duration when debugging has completed. |
Status Message | Details of step or process status, corresponding to the Status Indicator. |
Tip:
The End Time and Duration options share a column in the table. You can choose which to show by right-clicking anywhere in the table and selecting Toggle between End Time and Duration. Designer retains your setting until you change it again.
Debug exceptions appear in the Trace view. If you want to see more of the error information, hold the cursor over the error row. Designer displays extended error data, including a stack trace, if appropriate. You can copy the text in the window. Press the F2 key for focus (after the window has focus, the prompt to do so disappears), and then CTRL+C to copy. The text is highlighted in blue after it has been copied, so you know when you can paste.
If you stop debugging a process in response to a prompt that you have reached the
Peak Memory Use (percent) setting as described in
Configuring Process Debug Preferences,
Designer adds a descriptive row to the Trace view.
The Trace view reflects the process in the active process editor.
Note:
The Trace view must be active for its shortcut keys to be enabled.
If you close the Trace view and want to reopen it, click
Window > Show View > 
Trace.
Related Topics