Description:
Phase 2 completes thedata deletion programme and delivers the user-facing experience.
Building on the engine and ITGS deletion support from Phase 1, Phase 2 adds deletion coverage for Warehouse (Power BI reporting data) and Marketplace (third-party connector data), and delivers the Excel-driven UI that authorised users will actually use to trigger deletions — with a full two-person approval flow and permanent audit trail.
Phase 2 cannot begin until Phase 1 is fully complete. The deletion engine built in Phase 1 is the backbone every feature here depends on.
What is being built in Phase 2:
Feature 3 — Warehouse Deletion and Refresh
When a packet is deleted from Core, its data must also be removed from the Warehouse — otherwise it continues to appear in Power BI dashboards, which is a GDPR violation. This feature deletes the matching Warehouse records and triggers a forced Power BI dataset refresh so the data disappears from reporting immediately.
Feature 4 — Marketplace Deletion
Packets that pass through Marketplace connectors may hold associated data in third-party systems. This feature identifies that data, calls the appropriate Marketplace connector to remove it, and confirms deletion before Core removes its own records.
Feature 5 — Excel-Based Deletion UI
The front-end that authorised users interact with. A user with the Purge Packets permission uploads an Excel file containing the packet references to be deleted. The system validates the list, resolves the full consequential deletion group, and shows the user exactly what will be deleted before anything happens. A second authorised user must approve. On approval, deletion runs asynchronously across all 5 systems — Core, ITGS, Warehouse, Marketplace, and Blob storage — and a permanent audit record is created.
⚠️ Important — nothing in this feature is available until all 5 features are complete:
Even when Phase 2 features are individually built, the end-to-end deletion flow requires all 5 features across both phases to be live. The Excel UI (Feature 5) is the trigger point — it will only be enabled once Features 1 through 4 are confirmed complete and tested.
This feature will only be available to use after all 5 features across Phase 1 and Phase 2 are complete.
This is Phase 2 of 2. Phase 2 depends entirely on GDPR Data Deletion — Phase 1: Core Engine & Intelligent Search [https://feedback.enate.net/feature-request/p/data-deletion-packet-purge-framework-phase-1]