Description:

The front-end feature that authorised users interact with to trigger a deletion. The user does not search for packets manually — they upload an Excel file containing the packet references they want deleted. The system validates the list, shows them exactly what will be deleted (including all consequential packets in the group), requires a second authorised user to approve, and then executes the deletion in the background.

What it does:

Upload flow:

A user with the Purge Packets permission uploads an Excel file containing packet references

The system validates the file format and each reference

Invalid references are flagged with a reason so the user can correct and re-upload

Review flow:

Valid references are resolved to their full deletion groups

The user sees a full list of everything that will be deleted before any action is taken

The user adds a mandatory deletion reason from a controlled dropdown

Approval flow:

A second authorised user (different from the submitter) reviews and approves or rejects the list

Rejection returns the list to the submitter with a reason

Execution flow:

On approval, deletion is queued and runs asynchronously in the background

when complete A full audit record is created showing: who submitted, who approved, what was deleted, when

Dependency: Feature 1 (Packet Group Deletion Engine) must be complete for end-to-end testing. Upload and status screens can be built in parallel with Features 2 and 3.

Belongs to EPIC: Data Deletion — Packet Purge Framework [https://feedback.enate.net/feature-request/p/data-deletion-packet-purge-framework]