Using the Rule Debugger
- Updated on 09 May 2013
- 1 minute to read
Rules evaluate a data input and return an outcome. The outcome is dependent on whether or not the input satisfies the rule's conditions. Before using a rule in a production scenario, it is useful to test it with the Rule Debugger .
To use the Rule Debugger, open the rule you would like to test in the Rule Designer and click the Debug Rule link at the top of the screen. The debugger will prompt you to supply any required inputs before allowing the rule to run. Resulting outcomes or objects will be reported afterward, along with detailed data about each condition.
Our example rule expects two inputs: a string called Email Address and a Boolean called Can Use Portal . Our rule is set up to evaluate these inputs against the following conditions:
Does Email Address belong to the "yahoo" domain - which is to say, does it contain the string "yahoo.com?"
Is CanUsePortal set to "true?"
If both inputs satisfy their respective conditions, the rule will return an outcome of "true." If either or both inputs do not satisfy their respective conditions, the rule will return an outcome of "false".
Begin by opening our rule for editing in the Rule Designer . Near the top of the window, click the link Debug Rule .
Our debugger's first action is to prompt us for inputs.
Set the Can Use Portal parameter to "true" by checking the box
Supply an email address of email@example.com before clicking Run to begin our debugging session.
Since the inputs satisfy both conditions of our rule, the debugger returns a value of True .