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.
Posted: 1 year ago
Posted: 22 Aug 2019 7:33 EDT
Vikash Ranjan Karn (Vikash Karn)
Senior Technical Solutions Engineer
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.
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.