Customize purge and Archival process


Is there a way to customize the Purging process in Pega? We are in 8.2.2 version. I can only see a wizard to select the class group and age.

We would like to filter on status (as the cases closed with custom status - doesn't start with Resolved-) as well as few exposed properties from the work object.

Any idea how to implement this is appreciated.




Keep up to date on this post and subscribe to comments

August 21, 2019 - 5:28pm

Hi Veera,

Purge/archive uses java API calls and the activity that triggers them is ProcessConfig which is a final rule.

So i don't think you can customize the purging process. 

One thing that you can do if it meets your business requirement is that you can change the pystatuswork column value in the DB  to "Resolved-custom" i.e your custom status prepended with "Resolved-"

Please try this and let me know the result.




August 22, 2019 - 4:35am
Response to Vikash Karn

Thanks for your message Vikash. 

Looks like it is more restricted. Not only the status we also need to check one of the exposed custom property to be included in the Purge logic. Based on the property value we should determine the number of years and delete the cases older than those many years.

We are looking forward to achieve this using Pega purge process.




August 22, 2019 - 7:33am
Response to VeeraSaddala

It uses pxresolvedtimestamp property to qualify any work object for purge based on the value you have given (work object older than) in the wizard.

So when you are setting the pyworkstatus with your custom value then this property(pxresolvedtimestamp) will be empty, so you should set this value as well to currentdatetime when resolving the work object with your customer status.

For now you can try the below and check if that works or not:

1. Set the pyworkstatus as "Resolved-custom".

2. Set the pxResolvedTimestamp with a value which makes this work object available for purge.

3. Run the Purge and archive wizard.

Please let me know the result of the same.




October 7, 2019 - 9:45am
Response to Vikash Karn

Hi Vikash,

Thanks for your message and sorry for the late response. I have checked the pxresolvedtimestamp for the cases resolved with custom status. I don't see the property has a value. We do have few case types resolved with the status "Resolved-*". This property is set in the page list : pyWorkPage.pxResolveSummary(1). Please confirm this is the right property.

I believe we can have an agent to update the status for the old cases (to Resolved-*) as per our business criteria and schedule the Purge activity as well.

However for the cases where this property: pxresolvedtimestamp already updated, we still need to find a way to customize the purge process itself to pick the cases on criteria (filter on a property value from clipboard) to complete the purge.