@PadmaK42  as far as I can tell there is no OOTB capability.

Is this requirement not satisfied by Documenting your application ?

A developer can view the generated Java code of an activity without opening the rule form by selecting Actions > View Java. This will display an approximation of the generated Java code created by the rule instance. This feature is available for certain rules, including activities, when rules, and stream rules, if the developer has the @baseclass.ToolbarFull privilege. Please note that the Java code presented is similar to, but not identical to, the Java code that executes at runtime. The runtime Java code includes inline Java code from other rule instances and reflects rules in the requestor's RuleSet list.

We rely on the capabilities of Directly Capture Objectives (DCO) to document code:

https://www.pega.com/products/platform/directly-capture-objectives

https://community.pega.com/blog/how-pega-88-can-improve-your-impact-pega-business-architect

 https://www.pega.com/insights/articles/what-pega-dco

In Pega Platform, there isn't a specific method used to document the code. Instead, Pega uses a model-driven approach called Directly Capture Objectives (DCO) to visually capture business requirements, rules, data models, UIs, integrations, reports, and organizational structures. This approach allows business and IT to collaborate using a common visual model, and Pega 7 automates the code generation. As the requirements change, a change in the model equates to an immediate system change. Documentation is automatically generated from the model and always reflects what the application actually does. This eliminates the need for manual code documentation and ensures that the application and business requirements are always in sync.

Also see a similar question that was posted in How to get the source code for an Activity