For aggregate properties you can simply select those properties you want to track in case settings. After that any change in those fields you can see the pagelist name as a link on clicking on the link we can see the changes happened on the fields. Major issue in pagelist properties in OOTB field level auditing is we can’t determine which page got updated we can’t see which index of pagelist got updated. To achieve we need to add a logic in pysave ootb activity in FLAudit- class. There we need to add our logic to get identify which row got updated. For example I have 3 pages in pagelist and it as id name and age as fields. Now I have updated the age in 2nd page. So based on id we can identify which row got updated we need to get the id of the row which got updated and save it in the flaudit class. Then we can show that value in history tab so users can see which row got updated
nice explanation
Thank you Gurujii
Thank you😊
How about for aggregate properties and data class properties can track??
Data class has separate history table.
Managing Pega Data Type History Snapshots #pega #Pegadev #pegahelp
th-cam.com/video/-KLN5QUFy2E/w-d-xo.html
For aggregate properties you can simply select those properties you want to track in case settings. After that any change in those fields you can see the pagelist name as a link on clicking on the link we can see the changes happened on the fields. Major issue in pagelist properties in OOTB field level auditing is we can’t determine which page got updated we can’t see which index of pagelist got updated. To achieve we need to add a logic in pysave ootb activity in FLAudit- class. There we need to add our logic to get identify which row got updated. For example I have 3 pages in pagelist and it as id name and age as fields. Now I have updated the age in 2nd page. So based on id we can identify which row got updated we need to get the id of the row which got updated and save it in the flaudit class. Then we can show that value in history tab so users can see which row got updated
nice explanation