We want to audit each search that happened via the search and select pattern - search criteria , search parameters and the results; not only the record that is selected.
Currently these values are not actively stored in clipboard for field audit to happen.
Are you looking to implement Search and Select pattnern to work history table?
Hi @Aditi_Mehta
For Pega DB queries, you may want to try the pyRetrieveReportDataExtension activity (v25 onwards) which executes for every report definition call with proper conditions of the report name, view which this call came from, etc and then you can log/audit the entries as per your requirement. Not sure if other community members have any better ideas.
For search and select tables hitting external systems via Connect-Rest, you can check the below post. Although i have not tried this myself.
Hope this helps.
Regards
JC
Any sort of auditing would work.
If this intended for certain search and select pattern, then we could have the wrapper data page that calls data transform to add logging to certain table and then perform the search using the Connector or Report definition.
If this is intended at global search, then I’m not sure if there are extensions available as part of Search and Select?
Just curious to know, why do they want to store/audit the search parameters, results and selections? for training? or other reasons?
It is intended for each search and select pattern which is across 22 intents and interaction. Since this is a customer service application, auditing is necessary for reporting and tracking.
The wrapper data page approach is not scalable in our scenario.