Reopen Request UI
Summary
Employees request corrections; reviewers approve or reject pending requests.
Audience
- Employees, managers, administrators, developers, QA engineers, and support engineers as applicable
Purpose
Employees request corrections; reviewers approve or reject pending requests.
Navigation Path
Employee punch weekly board; reviewer Attendance board.
Intended Users
Source-defined navigation audiences and API authorization determine access; see Navigation and access.
Preconditions
Existing date context; authenticated employee or reviewer; no duplicate pending request.
Main Components
Reopen modal, requested status/hours/overtime/reason; pending badges; reviewer queue/modal.
Columns or Fields
Date, current/requested status, requested work/overtime and reason.
Filters
Employee week navigation; reviewer pending list.
Actions
Submit request; approve or reject pending request.
Validation
Reason is required; future-date and duplicate-pending restrictions are enforced by backend; locked-period approval is rejected.
Loading State
Parent workspace loading state.
Empty State
No pending requests produces no request rows/badges.
Success State
Success toast and Attendance refresh.
Error State
API error surfaced via safe toast/inline fallback.
Access Behavior
Self and reviewer scopes are enforced by API; UI evidence is Transitional across surfaces.
API Dependencies
My/pending reopen, create, approve and reject operations.
Related Business Rules
Approval recalculates and checks Payroll lock; rejection publishes no Attendance lifecycle event.
Screenshot Placeholder
Capture later from a safe non-production environment using synthetic data. Remove identifiers and personal details before publication.
Source References
UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsxUI/salary-ui/apps/client-hrms-portal/src/App.tsx
Related Articles
See Also
Keywords
- Attendance UI
- React
- User workflow
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly