Global Cleanup Logic in External Purge Process

The external purge functionality in B2BI has shown significant improvement compared to the internal purge mechanism. However, further enhancements are needed to ensure the database and file system remain lightweight, scalable, and cost-efficient in the context of growing business demands.

Currently, there are multiple transactional tables/features governed by various purge settings spread across different properties. The inconsistency of the purge settings leads to orphaned records in several transactional tables—which is evident in DB Stats Report.

This enhancement request is to implement a final catch-all purge mechanism within the external purge process. This mechanism should delete all data older than a defined global purge setting, regardless of:

• Whether a business process is indexed or not

• Its eligibility based on current purge settings of a feature

• AssociateBPsToDocs has linked a document with a business process or not

• ACT sessions expired or not

• Admin Audit

• User news expired or not

• Mailbox Messages extracted or not

• logs

• SFG activity records, etc.

This cleanup should cover all relevant transactional tables (e.g., trans_data, document, workflow_context, bpmv, usernews, act tables, etc.) and associated file system storage.

Implementing this functionality is critical to maintaining system performance, simplifying solution maintenace, and minimizing infrastructure costs.