1

Starts/pauses the debugger.
If the debugger is started, the possibility to add breakpoints in blocks of event handling is activated automatically.
Breakpoints can be activated in blocks via right-click or the '...' menu. Blocks with breakpoints are highlighted graphically.
Behaviour and actions can set a breakpoint via the symbol.

If the block with the breakpoint is executed next, the debugger pauses the execution for analysis purposes.
The debugger automatically moves to the foreground in the process.

If the debugger is paused, it will no longer stop at any breakpoint, though these will remain untouched.

2

Lists all active breakpoints.
The names of the breakpoints consist of an abbreviated type name (e.g. AEHC for event handling), the ID of the containing configuration and a consecutive counter (for the behaviour of the behaviour name).

3

Stops the debugger and discards all breakpoints in the process.

►NOTE◄ As long as the debugger is not explicitly stopped, all breakpoints are retained, even if the client is reloaded. Only an explicit logout from the client stops the debugger automatically.

4

Restricts pausing at breakpoints to selected sessions.

• Restrict to own session (default) - it will be paused only if the breakpoint is reached within the users' own session.

• Restrict to user (only applies to event handling).
  

  

  
  
  It will be paused only if the breakpoint is reached within the session of one of the specified users. Thereby the user's own session can be additionally excluded if debugged with one of the mentioned users.

5

Shows all breakpoints that are currently paused. The name of an entry consists of the abbreviated type name (e.g. AEHC for event handling), the ID of the containing configuration and a consecutive counter, as well as the user name of the session and a source (for the behaviour of the behaviour name).
By selecting another session entry the debugger dialog shows the corresponding states (7) of this breakpoint.

6

These functions can be used to decide in a granular way whether and how to continue at a paused point.

• Resume – Cancels the pause and stops again only when the next breakpoint is reached.

• Step – Continues execution until the next block at the same level.

• Micro step – Jumps into the paused block and pauses at the next subordinate block.

• Resume all – Similar to 'Resume', with respect to all currently paused breakpoints (5).

7

Shows the state of the input data (result), all variables and the current log messages.

►NOTE◄ For behaviour, the 'Variables' tab shows no entries and the 'Log' tab shows only the element ID of the triggering element and the type of interaction (e.g. MANUAL_CHANGED if the user triggered their own behaviour).