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 strategy rules by using the Tracer tool

Suggest edit Updated on April 5, 2022

You can use the Tracer tool to view the order in which the top-level strategy and its substrategies are processed in your application. The outcome of the analysis can give you insight about the correctness of the strategy configuration.

For example, with the Tracer tool, you can detect a faulty switch condition that prevents a substrategy from running or that unnecessarily triggers a substrategy.

Using the Tracer tool to view the order in which strategies are processed

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Decision category, and then click Strategy.
  3. From the rule list, select a strategy to analyze.
  4. Click Tracer to open the Tracer tool.
  5. In the Tracer window, click Settings to open the Tracer Settings window.
  6. In the Event types to trace section, select Strategy.
  7. Click OK to save the trace criteria and close the Tracer Settings window. Do not close the Tracer tool.
  8. On the Strategy form, click ActionsRun.
  9. In the Run window, click Run.
  10. In the Tracer tool, analyze the run results.For example: By using the preceding procedure, you can analyze the following multilevel strategy:
    Example of a strategy with multiple layers of substrategies
    A multilevel strategy has two substrategies.

    When the strategy is run, it returns the following results in the Tracer tool:

    Multilevel strategy sequence of processing as seen in the Tracer tool
    The Tracer tool results contain six entries that represent
                                        the processing of strategies in a sequence.

    The results show that the application processes the strategy in the correct sequence. The strategies started in the following order: S1, S2, S3. The strategies were completed in reverse order: S3, S2, S1. This behavior is a result of the following strategy configuration:

    • Strategies are processed in descending order from the top-level strategy.
    • A strategy finishes processing after all its substrategies are complete.
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