1.7 KiB
1.7 KiB
ADDED Requirements
Requirement: Agent Registration Application List
The admin frontend SHALL provide a paginated agent registration application list with the documented filters and backend response statuses.
Scenario: Filter registration applications
- WHEN an authorized user selects status, time, phone, keyword, parent shop, or submission anomaly filters
- THEN the frontend MUST send those filters to
GET /api/admin/agent-distribution-registrations - AND the list MUST display business, approval, and submission status names from the response
Requirement: Agent Registration Application Detail
The admin frontend SHALL provide a detail page for GET /api/admin/agent-distribution-registrations/{id} and display the complete registration information returned by the backend.
Scenario: Open registration detail
- WHEN an authorized user opens a registration application
- THEN the frontend MUST request the application detail by ID
- AND MUST display the phone, address, shop, distribution code, business status, approval status, and submission status
- AND MUST NOT display password or internal approval fields not present in the response
Requirement: Recover Agent Registration Approval
The frontend SHALL expose POST /api/admin/agent-distribution-registrations/{id}/recover-approval only when recoverable = true and the user has the recovery permission.
Scenario: Recover approval
- GIVEN a registration response has
recoverable = true - WHEN the user confirms “恢复审批”
- THEN the frontend MUST call the recovery endpoint with only the registration ID
- AND MUST refresh the detail after success or a state conflict