Case Archiving - Policy inheritance at class level
Hi all,
We are implementing case archiving as described here.
Our case hierarchy is as follows (note all the cases share the same class group):
- MyCo-Work-Dummy
- MyCo-Work-Dummy-UpdateCustomerName
- MyCo-Work-Dummy-UpdateCustomerPhoneNumber
- ...
- MyCo-Work-Dummy-UpdateCustomerAddress
All of these implementation case types share the same archival requirements.
Therefore, we created a single Data-Retention-Policy instance (archive policy) under the parent class MyCo-Work-Dummy, expecting the implementation classes to inherit it.
However, when we ran the archival job using the pyPegaArchiverUsingPipeline job scheduler, none of the implementation cases were archived.
Question:
- Is defining the archival policy at the parent (or framework) class level supported by Pega? Or should we create a separate archival policy under each implementation case class?
HCA Healthcare
US
@ClaudioR Pega doesn’t inherit archiving policies by class, so a policy on MyCo-Work-Dummy won’t apply to the child case types. Create the same Data-Retention-Policy in each concrete case class and make sure Applies To matches that exact class. Check that your conditions (status and days since resolved) match real cases you expect to archive. Turn on and run the pyPegaArchiverUsingPipeline job scheduler and run it in the System Runtime Context so it can see your rules. Set any required DSS for pipeline mode if your setup needs it. After a run, review Admin Studio → Archival Summary to confirm what was archived. If you want one place to maintain logic, reference a shared When or Decision rule from each policy.