Purging Configuration: ETL vs Archiving in Clevest

We are implementing data purging in our Clevest Test environment and need clarification
on the recommended approach before moving to production:

Current Setup:
- Active Archiving feature
- ETL Data Warehouse task running every 15 minutes (non-one-to-one mapping)
- Web frontend purging feature available

Questions:
1. Should purging be configured via Archiving or ETL?
2. What is the recommended sequence: Archive → Purge → ETL, or another order?
3. How do we ensure all source data is captured in the Data Warehouse before
purging from the source database?
4. Does the system automatically archive before purging, or must we manually
coordinate this?


Thank you,