Salesforce

Controlling Project Execution (Magic xpi 3.x)

« Go Back

Information

 
Approval Process StatusPublished
Objective
Description

Controlling Project Execution (Magic xpi 3.x)

During the Debug session you can control the execution of the project in several ways:

  • Setting Breakpoints

Breakpoints are a helpful debugging tool. They let you stop execution of the flow on a specific step in order to examine the Context View and Activity Log.

Once a breakpoint is reached, all the executed contexts, such as threads and branches, are stopped before they execute the next step. The Debugger then waits until the user selects Step or Continue. Breakpoints can also have a condition that conditionally sets the breakpoint based on a variable, environment variable, etc. The expressions are like any other expression in the project; however, they are not part of the Cross Reference, Text Search, and Checker processes, since they are saved outside the project sources.

  • Suspending Steps, Flows, or Business Processes

When debugging, you may wish to suspend certain elements in order to better pinpoint a problem.

A suspended step will be ignored and the Debugger will continue to the next step as if the step was executed.

A suspended flow will not be executed and will be considered “stopped” until released from that mode.

The same method can be used to suspend a flow or branch.

The project ibp file created by the Debugger overrides existing ibp files created previously by the Debugger or by the Re-Build All option. If you only want to debug a specific flow, it is recommended that you use the Flow Debug option. This option is accessed from the flow's context menu in the Navigation pane. Alternatively, you can set any flows that you do not want to debug as inactive.

Note:

  • When debugging a single flow (by right-clicking on the flow and selecting Debug), the first execution of the flow is carried out as if the flow was set to Autostart. 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 execute the project in Server mode after the Debug session, you need to rebuild the project again using the Re-Build All option.
    A project which was built as part of the Debugger process will not be executed in Server mode. The Server will terminate the project and a message will appear in the ifs.log file.

Reference
TitleControlling Project Execution (Magic xpi 3.x)
URL NameControlling-Project-Execution-xpi