Debugging a Project (Magic xpi 4.9)

When you start the Debugger you use the menu options to begin the debugging process. You can debug a project in the following ways:

• Debug the entire project.

• Debug a project or part of a project (one step at a time).

• Debug a single flow. You do this by right-clicking on the relevant flow, and selecting Debug from the context menu. In this mode, the Debugger will execute the selected flow and all of the other flows in the project will be inactive for this project, including all of the flows called by it. This mode will not affect flows in Suspend mode. It is the user’s responsibility to handle these flows. The Debug flow option will be enabled only for Servers that are not running. In addition, Attach mode will not be operational in this mode.

When debugging a single flow, the first execution of the flow is carried out immediately as if the flow was set to Autostart. When the flow execution is completed once, any defined triggers will wait for external events. If this flow contains a trigger, the flow will be executed twice. The first execution is caused by Autostart without involving the trigger, and the second execution is due to the trigger itself.

To start debugging:

1. From the Debug xpi menu, select Start Debugging, or click from the toolbar.

2. Magic xpi opens the Debug mode. A new set of options is available in the Debug xpi menu and a new set of icons is displayed on the right side of the toolbar.

3. Begin the debugging process. In the Debugger environment, you can:

• Select Run from the Debug xpi menu,or right-click in the Context Tree and select Run from the shortcut menu to debug the flow selected in the Navigation pane. The Debugger will run in Auto mode.

• Select Step from the Debug xpi menu, or right-click in the Context Tree and select Step from the shortcut menu to debug the specific step. The Debugger will debug the step selected in the Context Tree or in the Flow view. You can also right-click on a step in the Flow view and select Step from the shortcut menu.

• To debug an entire project, select Run from the Debug xpi menu when the cursor is on the Business Process.

The On-premise type projects will not be debugged on the Cloud even though the user is logged-in to the Cloud. The user has to explicitly convert the project type to Cloud to enable the project debugging in the Cloud. To do the same, go to the File menu in the Magic xpi studio, select the Convert option and change the project type to the Cloud type and then start debugging.

To stop debugging:

• Click Stop from the Debug xpi menu to stop the Debugger without saving the current Debugger environment.

• Select from the toolbar or select Close or Detach from Server from the Debug xpi menu to exit the debug environment and save the current Debugger environment automatically. You will not be asked whether to save the environment if you use this option.

If you are in Open mode, this stops the Debugger and returns you to Edit mode.

If the project is running or is attached to a project, when you select Close, the project is closed/returns to production mode.

After a Debug session and before trying to run the project in Server mode, make sure to execute the Build Solution or Rebuild Solution procedure again. The executable file created during the Debug process cannot be used for deployment. A temporary ini file called DebugSRV.ini is created under the project directory when you start the Debugger. It is deleted when the Debugger is stopped.

Related Topics

Debugger Settings

Attach to Project

Setting a Breakpoint

Suspending a Flow, Branch, or Step

Breakpoints and Suspends Pane

Context View