Stepping through the rule execution code

You can use the Debug Perspective to step into the code to debug a rule.

Before you begin

Note the following before doing the procedure:
  • You cannot step into Java™ code if the rules are run in sequential mode. When debugging, you can step into the BOM-to-XOM code, even if the sequential mode is used.
  • In decision engine rule projects, the BOM-to-XOM code is in the Advanced Rule Language (ARL) and does not support breakpoints.

About this task

Several stepping options are available.

Procedure

To step into your IRL code:

  1. Click Run  > Debug Configurations.

    The Debug Configurations dialog opens.

  2. Select your configuration in the Configurations pane.
  3. Make sure that you select the Stop at first rule statement check box.
  4. Click Debug.

    The Debug Perspective opens and execution stops at the first rule statement to be run.

  5. Several stepping options are available to you:

    • To call the next expression and suspend execution at the next unfiltered executable line, click Run  > Use Step Filters or click the Use Step Filters button. You can also press Shift+F5.

    • 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. You can also press F5.

    • 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. You can also press F6.

    • 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. You can also press F7.