I recently had an open SR with Pega on this regarding the same. Here was the outcome:
I was advised not to use this because its deprecated/no longer supported. I understand it also causes the generation of lots of unnecessary files/performance issues.
The correct way is to customise using list view GetArchivableItems as you stated above
Case type archive / pyPegaArchiver
There is currently no way to configure anything other than the "time since resolution" on the Case Type Archival Settings. This is a limitation of the product. I believe there isn't a plan to extend this in the near future.
I had to develop my own in-house utility to achieve what was required for GDPR regulations.
Posted: 7 months ago
Updated: 7 months ago
Posted: 2 Mar 2021 22:45 EST Updated: 2 Mar 2021 22:49 EST
Chetan Chaudhari (chauc)
Sr. Product Manager - Data Engine
@sarah GODFREY , we're considering adding support for legal-hold i.e. excluding certain case from archival process in 8.7. Cases could then be skipped during archival/purge and also from permanent deletion i.e. expunge. So such cases would continue to exists in primary database, if they are not yet archived, and in secondary database, if they were already archived.
This is available in the new archive/purge/data-retention functionality, that is currently available only on Pega Cloud.
Please let me know if you have other GDPR requirements. Also, can you let me know which SR was that?
I explored the new archive functionality for Pega Cloud on version 8.4.2, but since our GDPR requirements are more complex, the currently available archival criteria did not suffice for our GDPR requirements (need more filter criteria than just Resolved cases after X days).