You can enable DEBUG Logging for activities by means of the "Set Logging Level" feature. I'm not sure what you're trying to trace, but you will see entries in the PegaRULES log file for every process that runs that activity. The actual name to enter can be found by typing the activity name and waiting for autocomplete to show you the proper name; this only works if the activity has run at least once since the JVM started. For example, the name to enter for "finishAssignment" turns out to be "Rule_Obj_Activity.FinishAssignment.Work_.Action"
Thanks for the response. I have a huge Pega application and difficult to identify the flow path for a business process. So, I would prefer to run the regression suite and capture all the flows and activities that got executed. Basically, I'm trying to collect the knowledge out of the tracer.
You're not asking if it is possible to just trace activities and flows, are you? Because that is a valid choice in the Tracer settings panel. You may also want to limit the rulesets to just your own, as you may have no interest in OOTB activities. I don't know how many regression tests you wish to Trace, but certainly you can start the Tracer and then run a test and analyze the Trace? And so forth, and so on?