About Tracer Options in Pega PRPC-2:

Option-1 Setting Break Points:

We will see about setting break points in the activities. This option is very similar to the breakpoints in Java.

Option -2: Setting watch variable:
To watch the variable in some page, so to check in which step what value is getting updated,

After setting the wtach variable for pxUpdateDateTime in pyWorkPage, we will trace and check how and where the date is updated.

We can see when watched variable is changed and it’s highlighted in the step where its updated.

About Tracer Options in Pega PRPC-1

Pages to trace Option in Tracer:

In tracer we can see only the Primary page or step page of that step, we cannot see the other pages values what changes are happening, it will be difficult to get that. So if we want to see the values, then we can use this option "Pages to tracer".


we need to add pages as same as in the images below.

In Tracer, when we trace our activities, then these added pages will be displayed in the tracer as below.

In this pyWorkPage is the Primary or Step Page, and we can see the other two pages which we added in pages to trace.

Note: Please give your comments below, if you have any suggestions.

About Tracer in Pega PRPC

About Tracer Tool in pega PRPC:

While programming what we will feel difficult is to debug the errors or values which is going wrong(either in development or in testing or in any environment).

Pega PRPC has given tools for making developers life easy. Tools such as Tracer, Clipboard and so on.

We will see about the tracer tool here below:

With Tracer, you can see the processing performed during run-time in summary or in detail. view or set the value of watch variables, and drill down to step-by-step details. You can view trace events for any requestor connected to your server node, not just your own session (if you know the connection ID of the session).

In Pega 7, you can see the tracer icon in footer. in Latest version, they are displaying Thread and Requestor id which the are tracing.

By using various Trace options, you can set very fine-grained control over what you wish recorded in the execution trace. You specify the applicable events, break conditions, and targeted RuleSets.


Troubleshooting
Sometimes, you may not see rows that you expect to see in the Trader results display; for example, steps for certain activities. A likely cause of not seeing any steps in the Tracer results is related to the Trace options being applied -- options set in either the Events to Trace or the RuleSets to Trace sections of the Trace Options window.

For example, the Tracer enforces RuleSet access controls.

Tracer output includes information only for rules in RuleSets that are checked in the the RuleSets to Trace section. So if the RuleSet that contains the activity is unselected in the RuleSets to Trace list, that activity's steps do not appear in the results

(Even when you trace a requestor session other than your own, the list of RuleSets you can trace is restricted to those available to your session. You can't use the Tracer to see execution of rules in RuleSets not available to you.)

If you do not see any activity steps in your Tracer results:

In the Events to Trace section, verify that the Start and End check boxes are selected for Activities and Activity Steps.

If you see some activity steps in the Tracer results, but not ones from certain activities:

In the Trace Options window, scroll down to the RuleSets to Trace section and verify that the RuleSets for those activities are selected.

Note: We will see more tracer options and Features in the Other upcoming posts.

Referenced from: https://pdn.pega.com/introduction-tracer-tool/introduction-tracer-tool