Question
Nordea
SE
Last activity: 16 Jan 2024 12:19 EST
Pega Archiving Support
Hi,
We are exploring Pega OOTB Archiving and purging as explained here - https://docs.pega.com/bundle/platform-88/page/platform/system-administration/case-archival-expunge-details.html and we are now doing some impact analysis based on below questions before we can adapt this feature:--
1) I understand when we retrieve archived case, it displays data in read-only mode. Will this have any impact if we upgrade pega platform or change UI architecture (say moving from traditional UI to constellation architecture)
2) Archival storage is determined from DSS rule - dataarchival/repositoryForStoringArchivedData. As we have several application sharing the same platform, can we seggregate this storage as DSS value is global and we don't want to store case data for all the application in one single directory
3) if in future if we decide to change the storage type (say we change from file storage to amazon s3) and move all the archived data to new repository, would we be able to retrieve the case details?
***Edited by Moderator Rupashree to add Capability tags***
Accepted Solution
Updated: 23 Jan 2024 7:29 EST
Pegasystems Inc.
CA
1. No Impact on retrieval of Archival case (as long as you have defined the views for Constellation to display the Archived case)
3. Pega archives the older cases based on your retention policy and stores all the archived cases in the File Storage(Amazon S3 for Pega Oncloud). Then the cases will be retrieved based on the elastic search.
I hope this helps!
Nordea
SE
@RameshSangili Thanks a lot for the quick response!
Regarding point no 3, let's say if we change the repository from Amazon S3 to Azure blob or file storage (for on-premise system), do you think retrieval will still work? I understand changing the repository may not be a very common scenario but still want to assess the risk associated with it.
Pegasystems Inc.
CA
I think it may not be straightforward to change the repository. Sorry, I am not aware of the risks involved once we changed the repository.