HR Dashboard (Vendor)
Nội dung này hiện chưa có sẵn bằng ngôn ngữ của bạn.
Executive summary
Section titled “Executive summary”Vendor HR Dashboard (/dashboard/hr) is the Clover-style workforce home for the selected store. It reads GET /vendor/hr/dashboard with optional store_id and timezone (store dashboard_prefs.timezone) so paid hours and shift buckets match the store calendar day.
The previous KPI dashboard remains at /dashboard/hr/v1.
GET /api/v1/vendor/hr/dashboard (hr module). Query:
| Param | Required | Purpose |
|---|---|---|
store_id | no | When set, attendance KPIs and shift cards are limited to that store |
timezone | no | IANA zone for “today / yesterday / last week”. Server falls back to UTC when omitted |
Existing fields (employees, attendance, leaves, late_arrivals_today) stay for the v1 dashboard. The v2 page also uses:
paid_hours.today/yesterday/last_week— decimal hours from production minutes (or clock-in/out minus unpaid breaks)shifts.now_upcoming— clocked in, not yet clocked outshifts.completed— clocked out todayflagged_timecards_count— overtime, late, uninformed, or missed clock-out on a prior dayupcoming_events— empty until a calendar feed is wired
Pass timezone with every dashboard fetch from vendor-web so the date header matches Timesheets.
UI notes
Section titled “UI notes”Shift tab, agenda vs timeline, and upcoming week/month are stored in the URL (shifts, agenda, upcoming). Overflow on a shift card opens Timesheets for that calendar day.