​​​​​​Hi,

We were exploring Pega Case Archiving feature as explained here (https://docs.pega.com/bundle/platform/page/platform/system-administrati…) and have following questions when we use File system as a repository:

1. When cases are deleted using the expunger job, restoring the archived file back to the file system does not help because Pega removes all associated metadata from the Elasticsearch index. This behaviour is also documented in Pega’s official guidance.
   • Is there a way to retain the Elasticsearch index data while cleaning secondary storage through the expunger job?
   • The reason for this request is that, in exceptional scenarios, we may need to restore data from cold storage (via our backup team) to secondary storage if a case is deleted by mistake and the business requires recovery. If the expunger job deletes everything, it seems there is no way to view the case data in Pega even after restoring the file
2. Out of the box, we only see a checkbox that purges all case data in secondary storage. What if we want to delete only specific data, for e.g., cases older than 3 years, while retaining the rest?
   • Is there an alternative approach within Pega to achieve this?
   • If not, the only workaround appears to be deleting archived files manually or via a non-Pega/cron job. Ideally, we would like each application team to manage housekeeping for their case data in secondary storage, and doing this through Pega jobs would make the process much easier.
3. In repository setting where we provide Resource path only accepts the hardcoded path name, is there way to generate this path dynamically depending on the application as each application may want to define their own repository path. Currently all case types are stored under one single folder