Question
JP Morgan Chase
IN
Last activity: 27 Apr 2022 9:56 EDT
Purge and Archival strategy
Hi Team,
Looks from 8.5 onwards ,pega is not supporting OOTB Purge & Archival wizard for on-prem deployments.
For developing a custom purge & archival wizard ,could you please list out the critical tables which should be included so that any referential integrity is not broken.
Assign-workbasket/worklist tables/work pool table
***Edited by Moderator Marije to add Capability tags***
Updated: 27 Feb 2023 4:40 EST
Pegasystems Inc.
GB
@GeorgeJ6156 could you specify which documentation contains the Purge and Archiving changes that you are referring to?
I'm assuming that the details come from this Purging and archiving old work items document.
Extract:
"Note: After Pega Platform version 8.5, the Purge/Archive wizard will no longer be officially supported. As a best practice, discontinue the use of this feature for on-premises instances and use your organization's database tools."
If you open the 8.7 documentation, the phrase reads as follows:
"Note: After Pega Platform version 8.5, the Purge/Archive wizard is no longer officially supported. As a best practice, discontinue using this feature and use the Case archival process instead."
This Case archival process is documented in article Managing your case archiving and purge process , The case archiving process, and Retrieving archived case data
@GeorgeJ6156 could you specify which documentation contains the Purge and Archiving changes that you are referring to?
I'm assuming that the details come from this Purging and archiving old work items document.
Extract:
"Note: After Pega Platform version 8.5, the Purge/Archive wizard will no longer be officially supported. As a best practice, discontinue the use of this feature for on-premises instances and use your organization's database tools."
If you open the 8.7 documentation, the phrase reads as follows:
"Note: After Pega Platform version 8.5, the Purge/Archive wizard is no longer officially supported. As a best practice, discontinue using this feature and use the Case archival process instead."
This Case archival process is documented in article Managing your case archiving and purge process , The case archiving process, and Retrieving archived case data
Are you using SRS (search cluster) in Pega 8.6? SRS (backward compatible with Elastic Search) will be supported in Pega 8.7 but not in Pega 8.6.
We suggested 3 options as mentioned below t
1). You can wait until Pega 8.7 for starting case archival.
For pr_perf_stats table with large data, truncation may be performed if required. Other work tables and related ones will likely not be large and not growing rapidly.
2). You can upgrade to 8.7 if they really need archival, as SRS supports archival in Pega 8.7
Regarding relevant tables in archiving, see document Trimming, purging, and archiving tables
Does this answer your question?
Updated: 25 Apr 2022 9:06 EDT
Pegasystems Inc.
US
@MarijeSchillern , adding to your reply!
@GeorgeJ6156 , I'm attaching schematics of tables that the new Case Archival feature archives in 8.7 and soon to be released 8.7.2. From 8.7 Case Archival supports On-premise clients who have PostgresSQL, Oracle, or MS SQL. We archived only resolved cases, so none of the case assignments related tables like Assign-workbasket/worklist tables/work pool are archived.
Many on-premise clients are upgrading to 8.7 to use the OOTB case archival instead of developing custom solution. I'm the Product Owner for Case Archival and can send you more documentation that you and your team can go through before making a decision on whether to build a custom solution.
If you have additional questions feel free to ask them here on this thread and our moderators will forward them to the relevant teams to help with any further required clarifications.
Thanks!
Pegasystems Inc.
US
@GeorgeJ6156, please reach out to your CSM from Pega to get access to the latest documentation on Case Archival.
JP Morgan Chase
IN
@Chetan.Chaudhari Hi Team, thanks for the directions ,but how about index tables ,are they handled by this OOTB archival feature.
Pegasystems Inc.
US
@GeorgeJ6156You mean to say Declare-index tables, right? Clients create them to optimize reporting, so unexposed properties can also be reported against. Those properties are anyway in the BLOB. Case Archival copies the BLOB in the archive, it means the data in declare-index tables is available in the archive. The rows in the declare-index tables corresponding to the cases that are archived in a run, are purged.