Looking for Archival strategies/solutions implemented for Pega Applications
As Pega has limited set of functionality for archiving and purging the case data through Archive and Purge Wizard, considering the basic functionality provided with this OOTB functionality, would like to know how various organisations are implementing/handling the archival & purging of case data and methods to access the archived data.
So, if you are aware/worked of any such implementations, can i request you to please outline the solutions that is implemented in your organisation/projects.
This information collected from various projects can be used to create a standard/recommended pega case archival solution, which can be cost effective and user friendly. We can also use this to request pega to come up with a feature or as an enhancement.
If it is already in place/documented would you be able to share the details here.
A new Case Archival capability was delivered early June just in time for PW2018. it is currently in production on Pega Cloud to support Agile Studio. It allows simple, in-the-model configuration for moving old cases to “cold” storage. Archived cases, along with associated attachments/history/pulse, can be searched and retrieved for display. Recommend not attempting to invent your own difficult-to-maintain solution.
Can you please tell me on which version on pega this feature will be available ? Also what do you mean by "Cold Storage" ? Is it going to follow the same existing behavior where the archived cases will be exported as "Jar" and it will be imported back when required for display ? Thank you.
In my last project we had some custom requirements regarding purging old cases.
1. We had to purge some data instances which were not work related.
2. Need to archive kpi data from the work before purging.
3. We need to skip archieving of old cases while purging as archieve does take a lot of time.
So, we have created an advanced agent for the same. We had created an schedule instance from the purge wizard. Then disable the default purge agent. Then we move the schedule instance to prod. From our agent we call the pega purging activity after we are done with data deletion and kpi archival.