Collection logging is deprecated after 7.1.7, can you help me to understand what will the alternative for that.
When the Save Execution Information? box on the Preamble and Stop tab is selected, execution of the Collect instruction causes execution details to be saved in a clipboard page named pxTraceCollection, an instance of the Log-Collection class. This page is saved, but not immediately committed to the PegaRULES database. Normal workflow processing typically provides the Commit operation later.
The key to a Log-Collection instance is formed from three properties:
Date and time of execution (property pxCreateDateTime).
Purpose — second key part — of the collection rule (pyPurpose).
Handle of the rule on which the collection was applied (pzInsKey).
The pyTop property on this page identifies the top-level collection rule that executed. Embedded pages (of property pyAction) identify the steps for rules that executed, in sequence. This page helps you identify steps not executed or executed more often than intended.
To present the page as a tree structure, run the standard activity Log-Collection.ShowCollectionSteps. The resulting chart identifies the elements of the collection
As a best practice, discontinue the use of these rules in your application, you can evaluate the functionality provided by the new,redesignedCollection form to identify opportunities for reuse. Please refer the below pdn article for detail information.