Salesforce

Debugging Options (Magic xpa 3.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Debugging Options (Magic xpa 3.x)

Both the Debug menu and the View menu provide you with a variety of debugging options.

The following options appear in the Debug menu:

Menu Option

Shortcut

Description

Run/Continue

F7

Runs the current program. When a breakpoint is reached, the entry appears as Continue.

Note: The Studio engine automatically loads the Runtime engine when it initially loads. However, this process is not visible to the end user until a request is made from the Studio to run something, such as pressing F7 to execute a program. Then, the Runtime engine is visible and active.

Run in Browser

Ctrl+Shift+F7

Runs the current program in the browser.

Run Project

Ctrl+F7

Runs the project.

Stop

Stops the runtime execution. This entry will be disabled if the project is not running in Debug mode.

The Stop button shows up as a red square on the overhead menu, in the Studio. While the Debugger is running, you can click on this, and the test will stop.

This is useful to cut short a long batch job, or to extricate yourself from an infinite loop.

Execution on Android

Enables the running of a program or project on an Android device or simulator. Since version: 2.4

See also Execution on Android.

Debug Mode

If you select this option, all execution will be run under the Debugger.

Break Now

Alt+Ctrl+F7

Breaks execution as if a breakpoint was reached. It allows you to stop a batch program at some point, then step through it.

This is useful especially in Online programs, so you can view the variables.

This entry will be disabled if the execution is not running in Debug mode.

Step

F10

Proceeds to the next operation in the current program.
If there is a call to another task, this will not be reflected in the debugging window.
This entry will be disabled if the project is not running in Debug mode.

Step Into

F11

Proceeds to the next operation in the current program, and, if the program calls a subtask or another program, starts debugging (stepping into) that subtask or program.

If the operation highlighted is not one of the following, it will behave as if the Step option was invoked: Call operation, CallProg function, Raise event synchronous (Wait=Yes), or Developer function calls.

This entry will be disabled if the project is not running in Debug mode.

Step Out

Shift+F11

Steps out of the current handler (and not the entire program) being debugged and returns to the next operation in the calling handler.

This entry will be disabled if the project is not running in Debug mode.

Toggle Breakpoint

F9

Adds or removes a breakpoint from the current operation.

If a breakpoint does not exist on this operation, a breakpoint will be created.

If a breakpoint exists and is currently enabled or is currently invalid, it will be deleted.

If a breakpoint exists and is currently disabled, it will be enabled.

You cannot define a breakpoint for a Remark operation. If an operation is changed to a Remark, its breakpoint will be deleted.

Add to Watch

Adds the variable to the Watch Variable list.
This entry is enabled when you are parked on a variable declaration (data view, handler or function).

Reset Runtime Engine

Ctrl+Shift+F9

Resets the environment, memory tables, Global variables, and shared values of the Runtime engine. This option can only be selected when the Debugger is not running.

This is useful when you want to "clean" your testing environment back to the state it would have if a user, say, just logged in.

Attach to a remote engine

Enables the debugging of an application that is currently being executed by a Runtime engine on a remote machine.
See also:
Remote Debugging

Detach from a remote engine

Stops the debugging of an application that is currently being executed by a Runtime engine on a remote machine.
See also:
Remote Debugging

The following options appear in the View menu:

Menu Option

Description

Activity Monitor

Opens the Activity Monitor, which lets the user log and display the command flow (such as tasks, levels, and operation flow) that occurs when executing a program.

Breakpoints

Opens the Breakpoint repository, which displays the breakpoints defined in the project.

Variables

Opens the Variable list, which displays the variables in the current runtime tree.

Call stack

Opens the Runtime Call Stack repository, which displays the state of the programs that are in the current runtime task tree and the handler that called the new program.

Running contexts

Opens the Running Contexts repository, which displays a list of the current open contexts.

Watch

Opens the Watch Variable list, which displays the variables currently being watched.

Reference
Attachment 
Attachment