We are unable to locate a list of expunged cases after running the OOTB Archival and Purging solution. Does the pyPegaExpunger job log the case IDs that gets expunged during its execution ? We need to provide proof of expunge to our data custodians and while we can run reports on Pega DB and also provide proof by browsing the Pega Cloud File Storage directories, we are looking for any OOTB mechanism that already gathers the proof. We have looked into Log-Archival Summary but it only provides the count of Cases archived, purged and expunged. While running the pzExpungeArchivedCase activity manually should log the Case IDs under Log-ExpungedCases, is there a similar logging when the pyPegaExpunger job is run ? We don’t see anything being logged under Log-ExpungedCases
no, pyPegaExpunger doesn’t persist a row-per-case list in Log-ExpungedCases; OOTB it only rolls up counts in Log-ArchivalSummary and writes run details to the repository/job logs. If you need case-level proof, you have two practical options: 1) turn on DEBUG for archival/expunge loggers (e.g., platform archival/expunger categories) so the job writes each pzInsKey it expunges to pegarules logs you can retain, and 2) wrap the job: create a small activity that iterates the candidate keys and calls pzExpungeArchivedCase with its logging flag, or writes each key to a simple Data- type, then have the Job Scheduler call this wrapper. Also keep the repository artifacts (archive manifests and the job’s run ID) alongside the DEBUG logs as your audit bundle. Bottom line: there’s no OOTB Log-ExpungedCases population from the scheduled job; you must enable logging or add a thin wrapper to capture IDs.
Enabled the following DSS that control expunge tracking:
dataarchival/expungeEnableTracking to true (default is false)
dataarchival/purgeForceLoggingEnabled to true
With this, the expunger job is logging the expunged Case IDs under Log-ExpungedCases. Tested in Infinity 24.1.2 version.