Stepping through the rule execution code

You can use the Debug Perspective to step into the code to debug a rule, except in sequential mode.

About this task

Several stepping options are available.

Note:

You cannot step into Java™ code if the rules are executed in sequential mode. When debugging, you can step into the BOM-to-XOM code, even if the sequential mode is used.

Procedure

To step into your IRL code:

Click Run > Debug Configurations.
The Debug Configurations dialog opens.
Select your configuration in the Configurations pane.
Make sure that you select the Stop at first rule statement check box.
Click Debug.
The Debug Perspective opens and execution stops at the first rule statement to be executed.
Several stepping options are available to you:
- To call the next expression and suspend execution at the next non-filtered executable line, click Run > Step with Filters or click the Step with Filters button.
- To call the next Java or rule statement and suspend execution at the next Java or rule line, click Run > Step Into or click the Step Into button.
- To call the next Java or rule statement and suspend execution at the next rule line in the next rule, function, or rule task, click Run > Step Over or click the Step Over button.
- To call the next Java or rule statement and suspend execution at the first rule statement of the next rule, function, or rule task, select Run > Step Return or click the Step Return button.