yanto/kulakpos_web
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update marketing
All checks were successful
Build, Push and Deploy / build-and-push (push) Successful in 5m14s
Details
Gitea Actions Demo / Explore-Gitea-Actions (push) Successful in 17s
Details
Build, Push and Deploy / deploy-staging (push) Successful in 41s
Details
Build, Push and Deploy / deploy-production (push) Has been skipped
Details

Browse Source
This commit is contained in:
eko54r
2026-05-14 11:55:22 +07:00
parent f80fcc4c1b
commit 05fd3230b8
448 changed files with 17545 additions and 5128 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
walkthroughs/2026-05-11_dc35a66c_Walkthrough__Attendance_Delegation_Fixes.md Normal file
View File

@@ -0,0 +1,21 @@
# Walkthrough - Attendance Delegation Fixes
I have completed the fixes for the attendance delegation module. These changes ensure that the mobile application can correctly fetch and display the attendance delegation history for employees.
## Changes Made
### Backend (ess_api)
#### [delegation-routes.js](file:///home/itc43/Documents/HOKBEN_PROJECT/ESS%20PROJECT/ess_api/ess_api/app/routes/delegation-routes.js)
- Corrected the handler references for `/api/delegations/attendance/history/employee` and `/api/delegations/attendance/history/employeedelegate`.
- They now correctly point to `delegationAttendanceServices.getAttendanceDelegationHistoryEmployee`.
#### [delegation-attendance-services.js](file:///home/itc43/Documents/HOKBEN_PROJECT/ESS%20PROJECT/ess_api/ess_api/app/services/delegation-attendance-services.js)
- Fixed a typo in `getAttendanceDelegationHistory` where it was querying a non-existent `status_approval` column. It now correctly uses `status`.
- Updated `getAttendanceDelegationHistoryEmployee` to include status `6` (Rejected) in the results. This allows employees to see their rejected delegation requests in the mobile app.
## Verification Results
- Verified that all route handlers are now valid function references.
- Verified that the SQL queries in the service layer are consistent with the database schema (using `status` instead of `status_approval`).
- The mobile app should now be able to fetch data from `/api/delegations/attendance/history/employeedelegate` without encountering "Internal Server Error" or empty results due to incorrect filtering.