Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting proposition filters

Suggest edit
Updated on April 5, 2022

To find the root cause of an error or unexpected results in a strategy rule, you can enable debugging for proposition filters. Use this feature for test purposes only because it negatively affects system performance.

Solution

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Decision category, and then click Strategy.
  3. Click the strategy rule that contains the proposition filter rule that you want to troubleshoot.
  4. On the Strategy tab of the Strategy form, double-click the Filter shape that references the proposition filter rule whose configuration you want to review.
  5. In the Filter Properties dialog box, select the Explain results check box.
  6. In the Store results field, press the Down Arrow key, and then select the property that stores the output value that the proposition filter returns.
    This property type must be TrueFalse.
  7. In the Store explanation in field, press the Down Arrow key, and then select the property that stores the values of propositions that the proposition filter evaluates at run time.
    This property type must be Text.
    Filter Properties window
    A warning for the Explain results option says that it
                                        reduces strategy performance and should be used for testing
                                        only.
  8. Test the strategy by configuring a single case test run or configuring a batch case test run.
  9. In the Results for strategy section of the Test run dialog box, review the eligibility result and message to understand why the filter proposition failed or returned unexpected results.For example: The strategy can return the following eligibility results:
    • Eligibility result: false
    • Eligibility message: (Default behavior = true) AND (RecentDroppedCalls = false) AND (LowChurnRateCheck = false)
  • Previous topic Tips for optimizing decision strategies
  • Next topic Troubleshooting strategy rules by using the Tracer tool
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us