Leave Approval and Rejection UI

Summary

The broader Leave request table provides row-level Approve and Reject actions; no dedicated approval queue or visible Workflow state was found.

Managers, HR administrators, QA, support, and developers.

Navigation: /leave → Leave Requests.
Context: table rows show employee, manager, type, dates, days, and status.
Approve: sends an Approved status update and reloads.
Reject: opens a modal, collects a reason, sends a Rejected update, and reloads.
Eligibility: the current client uses admin state, employee identity comparison, and Pending status. Final team scope and API authorization require confirmation.
Not present: bulk actions, dedicated pending-only page, balance-effect preview, attendance-conflict display at decision time, or visible Workflow-managed restriction.
Errors: page-level action error; success is refreshed status.
API dependency: compatibility status update. Direct service and Workflow behavior is documented in Workflow integration.
Screenshot placeholder: sanitized pending row and rejection modal.

The client does not expose enough state to claim that Workflow callbacks are reflected in real time.

Requirement	Confirmed behavior
Purpose	Apply a row-level approval or rejection decision.
Navigation path	`/leave` → Leave Requests → Approve or Reject.
Intended users	Users for whom the local decision controls are visible; final approver/team scope requires confirmation.
Preconditions	Loaded request and source-supported Pending/action state.
Main components	Request table and `ApprovalActionModal`.
Fields, columns, or sections	Employee, manager, type, dates, days, status; rejection modal reason.
Filters	Parent request status filter; no dedicated pending queue filter beyond selecting Pending.
Actions	Approve or Reject; no bulk action.
Validation	Rejection modal collects a reason; non-empty enforcement parity requires confirmation.
Loading state	No action-specific spinner confirmed.
Empty state	Empty request table.
Success state	Reloaded request status.
Error state	Page-level update failure.
Permission behavior	Client admin/identity/status visibility; API and optional Workflow are authoritative.
API dependencies	Compatibility status update; extracted Workflow may govern the runtime path.
Related business rules	Pending transitions, Attendance conflict at approval, balance effects, and Workflow restrictions.
Screenshot placeholder	Sanitized Pending row and rejection modal.