Reference > Rule Studio User Interface > Wizards > New Execution Trace Filters Wizard

This wizard defines new execution trace filters in Rule Scenario Manager.

To open the New Execution Trace Filters Wizard, in the File menu select New > Other, open ILOG Rule Studio, open the Rule Scenario Manager category, and click Trace filter properties.

Select Project Page

The Project page is where you select the Java project in which to create the new files. Select a project from the list.

New Execution Trace Filters Page

The Execution Trace Filters page allows you to specify the information to include in the execution trace. Note that a new execution trace filter will replace any existing one in the project. Excluding unnecessary data can improve execution performance.

Select the data items you wish to include in a trace by clicking them on in the list:

Table 27 Execution Trace Filters
Check box 
Default Filter 
Purpose 
Number of rules fired 
YES 
Returns the number of rules fired. 
Number of tasks executed 
YES 
Returns the number of tasks executed. 
Rules fired 
YES 
Returns the name of every rule fired. 
Tasks executed 
YES 
Returns the name of every executed task. 
Number of rules not fired 
YES 
Returns the number of rules in the ruleset that were not fired. 
Number of tasks not executed 
YES 
Returns the number of tasks in the ruleset that were not executed. 
Rules not fired 
YES 
Returns the names of the rules in the ruleset that were not fired. 
Tasks not executed 
YES 
Returns the names of the tasks in the ruleset that were not fired. 
Execution duration 
YES 
Returns the execution time in milliseconds (ms). 
Output parameters 
YES 
Returns the ruleset parameter values with the direction IN/OUT and OUT. 
Working memory 
NO 
The working memory filter is disabled by default owing to the large amount of data that it can return. It must be turned on manually. You can apply a specific filter to the working memory data. The filter is an inclusion filter, composed of a comma-separated list of classnames. For example: loan.Borrower, loan.Loan. 
Output string 
YES 
Returns the output data directly from the rule engine. 
Objects that triggered the firing of the rules 
NO 
Returns a list of objects that caused the rules to fire. 

Related Concepts

Execution Trace

Related Tasks

Tracing Ruleset Execution
Adding a Trace Filters File to a Project

Related Samples and Tutorials

How to Test Rules in Rule Scenario Manager Using Java Binding
How to Test Rules in Rule Scenario Manager using XML Binding