Our application is running on Pega cloud PRPC 8.5.2. We would like to utilize Pega offered cloud archival solution, as per documentation seems pyPegaArchiver extracts information and copies into Pega cloud file storage.
We wanted to know the following before proceeding with the approach.
How can we access pega cloud file storage, does it require to be purchased separately and is their any limitation for the same ?
How to access the work objects from Pega cloud file storage to show in review mode or to capture details in report definition or for the use of audit purpose ?
I have gone through the provided PDN documentation. So far i have been able to run archive/purge process for a case hierarchy with a top case and a few child cases, all the case instances have been archived and purged but when i review an archived case instances i cannot see the documents attached to the case. According to Archive/Purge documentation Link-Attachments and Data-WorkAttach instances should also be archived.
Is this correct? I mean, Do Link-Attchment and Data-WorkAttach instances get archived in zip file in s3 pegacloudfilestorage repository? If so, How can i retrieve them from archive file?
I will double check all the configuration archive/purge process again in case i am missing something and also make sure whether theData-WorkAttach-File exist for these respective cases from Link-Attachment instances as you mention.
If i do not find any explanation for not working after all i will raise a support request to look into it.
Answer: We advice clients to archive only those cases that would be required rarely, either if an audit were to occur, ora end-user were to come back. Archived cases would be in secondary storage and would not offer a normal access. These are old cases that have not been worked on after they were resolved for many months/years. . If clients need to perform a normal access like reporting, then they should not archive those cases. A business user would rarely care about metrics for cases closed several years/months earlier. In case a business user needs to compare latest metrics with older metrics, then reports should be run on historic data before archival, and saved for reference later.
Question: How are attachments handled for archived cases? Some applications have attachments in DB, others have it inS3 and few have it in DB + S3. Can the attachments be opened from an archived case?
Answer: We do archive attachments present in DB, and only the metadata about attachment is archived in case of pegacloudfilestorage/external/S3 attachments. If the attachment is already in pegacloudfilestorage/S3, it will remain there. The archived case would be able to continue to refer to it. Archived data is in S3, and pegacloudfilestorage also uses S3, so there’s no reason to move an attachment that’s already in pegacloudfilestorage. If an attachment is shared between two cases and both cases are not archived, the shared attachment won’t be archived. Attachment gets shared internally when Pega detects that two/more cases have the same file attached. All the types of attachments can be downloaded (DB, S3, shared/not-shared) after archival when you open an archived case for review.