Question


Swedbank
LT
Last activity: 11 Jul 2018 9:02 EDT
Pega Purge/Archive
Hi,
Purge/Archive is running everyday and should delete and archive 500 items everyday. White it could found all 500 item to work on it was working great.
Not it does not found so many items any more.
What could be wrong with these items the ones are failed, please see attached print screen.
could not found any info under feature description.
vygintas
***Moderator Edit: Vidyaranjan | Updated SR details***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution


Swedbank
LT
Hi,
I will try to explain why some of our cases were not Purged by PEGA wizard.
As you know Pega Wizard is purging Old (let say 90 days) with status contains -> "Resolved" cases.
But our application consist of Parent and Child cases.
And Pega Wizard Purging Parent cases that has Resolved time stamp earlier than 90 days with NO problem.
Hi,
I will try to explain why some of our cases were not Purged by PEGA wizard.
As you know Pega Wizard is purging Old (let say 90 days) with status contains -> "Resolved" cases.
But our application consist of Parent and Child cases.
And Pega Wizard Purging Parent cases that has Resolved time stamp earlier than 90 days with NO problem.
But if the Child case is also created from the Parent case, than PEGA wizard is waiting until Child case ResolvedTime stamp will be older than 90days.
That was an issue why some of our cases were not deleted.
We have created an agent/activity which sets a child cases Status to Resolved and also updates a Resolved Time Stamp, than PEGA wizard deletes all cases with no errors anymore.
Hope that will help.
Vygintas


Pegasystems Inc.
IN
Hello
Have you checked the log during the timeframe when the agent is running to perform purging? Anything interesting there?


Pegasystems Inc.
US
Hi,
If you are aware of the archive schedule timings, be sure to apply debug on the below activity class when it tends to fail.
Rule_Obj_Activity.ProcessConfig.PegaAccel_Management_Archival.Action
Enabling debug on above activity class provides the below details and you can discover if there are any errors with the instance itself or it's covered item or it's linked ones.
i. Which class is being processed
ii. which work item is being evaluated
iii. Check if there are any cover items
iv. No of instances of Link-, History-
v. Successfully added to processed list
vi. How long the process ran
vii. Total no of records processed, Failed etc.


Pegasystems Inc.
IN
Hi,
Kindly set the following logger to debug and you'll get related logs.
Rule_Obj_Activity.ProcessConfig.PegaAccel_Management_Archival.Action
This logger gives which class archival has started, what all work items are being evaluated, no. of cover items, No of instances of Link- and History-
Please go through below help documents also. It will give you full information regarding the purge/archive wizard.
https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
https://community.pega.com/sites/default/files/help_v731/procomhelpmain.htm


Auckland Savings Bank
NZ
Hi Chandrasekhar,
I have the same issue as for some cases it is working fine and for few it is failing. And as suggested I have added the Logger to debug and couldn't find much information.
It just provided the classes we are purging and cases acquired for purge, but some how it is not purging those cases. Any idea? (Below is the Log message)
Hi Chandrasekhar,
I have the same issue as for some cases it is working fine and for few it is failing. And as suggested I have added the Logger to debug and couldn't find much information.
It just provided the classes we are purging and cases acquired for purge, but some how it is not purging those cases. Any idea? (Below is the Log message)
2018-07-02 13:30:47,919 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (rgearchive.PurgeArchiveManager) INFO Dharma - Building processor for Purge/Archive with configuration Selected Classes:[ASB-Lend-Ops-AIMS-Work-GroupSchedule, ASB-Lend-Ops-AIMS-Work-LoanMaintenance, ASB-Lend-Ops-AIMS-Work-SinglePayment, ASB-Lend-Ops-AIMS-Work-Application, ASB-Lend-Ops-AIMS-Work-Refix, ASB-Lend-Ops-AIMS-Work-ChangeOfAdvisor, ASB-Lend-Ops-AIMS-Work-AdvanceCommission, ASB-Lend-Ops-AIMS-Work-GroupedPayment, ASB-Lend-Ops-AIMS-Work-Clawback, ASB-Lend-Ops-AIMS-Work-Restructure] All Classes:[ASB-Lend-Ops-AIMS-Work, ASB-Lend-Ops-AIMS-Work-GroupSchedule, ASB-Lend-Ops-AIMS-Work-LoanMaintenance, ASB-Lend-Ops-AIMS-Work-SinglePayment, ASB-Lend-Ops-AIMS-Work-Application, ASB-Lend-Ops-AIMS-Work-Refix, ASB-Lend-Ops-AIMS-Work-ChangeOfAdvisor, ASB-Lend-Ops-AIMS-Work-AdvanceCommission, ASB-Lend-Ops-AIMS-Work-GroupedPayment, ASB-Lend-Ops-AIMS-Work-Clawback, ASB-Lend-Ops-AIMS-Work-Restructure] Work Pool:ASB-Lend-Ops-AIMS-Work Threshold Execution Time (ms):600000 Maximum to Process:5 Commit Rate:10 Days Old:1 Process Outside Classes:false Process Only Resolved Items:true Is Archive:false Is Purge:true Purpose:TestPurge Export Path: 2018-07-02 13:30:47,920 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (essor.archive.WorkItemArchiver) INFO Dharma - Archiving is not enabled 2018-07-02 13:30:47,924 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (ocessor.data.WorkItemRetriever) INFO Dharma - Fetching work items took 4.138 ms 2018-07-02 13:30:47,925 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (essor.tree.WorkItemTreeBuilder) INFO Dharma - Building tree with root ASB-LEND-OPS-AIMS-WORK APPLICATION-733 2018-07-02 13:30:47,934 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (essor.tree.WorkItemTreeBuilder) INFO Dharma - Building tree with root ASB-LEND-OPS-AIMS-WORK APPLICATION-734 2018-07-02 13:30:47,942 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (essor.tree.WorkItemTreeBuilder) INFO Dharma - Building tree with root ASB-LEND-OPS-AIMS-WORK APPLICATION-737 2018-07-02 13:30:47,951 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (ssor.AbstractWorkItemProcessor) INFO Dharma - Max threshold reached. Purge/Archive processing to stop. 2018-07-02 13:30:47,951 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (processor.purge.WorkItemPurger) INFO Dharma - Nothing to purge empty set passed 2018-07-02 13:30:47,951 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (ssor.AbstractWorkItemProcessor) INFO Dharma - Purge Archive Total execution time in seconds 0 2018-07-02 13:30:47,951 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (cel_Management_Archival.Action) DEBUG Dharma - Running step 3_circum0 2018-07-02 13:30:47,951 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (cel_Management_Archival.Action) DEBUG Dharma - Running step 4_circum0 2018-07-02 13:30:47,951 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (cel_Management_Archival.Action) DEBUG Dharma - Running step 5_circum0 2018-07-02 13:30:47,951 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (cel_Management_Archival.Action) DEBUG Dharma - Running step 6_circum0 2018-07-02 13:30:47,951 [ PegaRULES-Batch-1] [ STANDARD] [ ] [TestASBAIMS:01.01.01] (cel_Management_Archival.Action) DEBUG Dharma - Running step 7_circum0
Accepted Solution


Swedbank
LT
Hi,
I will try to explain why some of our cases were not Purged by PEGA wizard.
As you know Pega Wizard is purging Old (let say 90 days) with status contains -> "Resolved" cases.
But our application consist of Parent and Child cases.
And Pega Wizard Purging Parent cases that has Resolved time stamp earlier than 90 days with NO problem.
Hi,
I will try to explain why some of our cases were not Purged by PEGA wizard.
As you know Pega Wizard is purging Old (let say 90 days) with status contains -> "Resolved" cases.
But our application consist of Parent and Child cases.
And Pega Wizard Purging Parent cases that has Resolved time stamp earlier than 90 days with NO problem.
But if the Child case is also created from the Parent case, than PEGA wizard is waiting until Child case ResolvedTime stamp will be older than 90days.
That was an issue why some of our cases were not deleted.
We have created an agent/activity which sets a child cases Status to Resolved and also updates a Resolved Time Stamp, than PEGA wizard deletes all cases with no errors anymore.
Hope that will help.
Vygintas