Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Configuring trace conditions

Updated on April 5, 2022

Before you run the Tracer tool, optionally configure trace conditions, based on the activity, data transform, rule, and so on, that you are testing and debugging. If you do not configure trace conditions, the default conditions are used.

  1. On the developer toolbar, click Tracer, or click ActionsTrace on an activity, data transform, or service rule form.
  2. Optional: Configure Tracer settings. Select which events, event types, rulesets, and pages to trace, break conditions, and options for the amount of output that you want the Tracer to generate.
  3. Optional: Send the Tracer output to a file. This option is useful if you want to work offline with the Tracer results instead of using the Tracer window.
  4. Optional: Set breakpoints to stop the Tracer at specific steps in activities.
  5. Optional: Set watch variables to detect when processing has changed the value of a property.
  6. Optional: Select a requester session other than your own current session to trace. By default, the Tracer traces your own requester session.
  • Configuring Tracer settings

    Maintain the quality of your application and quickly locate any issues by tracing selected events with the Tracer tool. Analyze the Tracer results conveniently by defining what information you want to include in the output.

  • Sending Tracer output to a file

    You can send the Tracer output to a file if you want to work offline with the Tracer results instead of viewing the output interactively in the Tracer window. In addition, you can suppress the event window to reduce network traffic and workstation load when you only want to view the output offline.

  • Setting breakpoints in the Tracer tool

    You can set breakpoints to pause processing for specific steps in activities. When a breakpoint is set for an activity, the Tracer window acquires focus when you or the selected requestor connection starts the activity.

  • Setting watch variables in the Tracer tool

    Set a watch variable to detect when processing has changed the value of a property. Focus returns to the Tracer window when your work changes the property value.

  • Selecting a session to trace

    By default, the Tracer traces your own requestor session. You can trace another session by using the Remote Tracer. The Remote Tracer lists every requestor that is connected to your Pega Platform server.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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