Summary
Select the release feature from the table below to be taken directly to that section of the release note.
Feature 1 | Feature 2 |
NYC Spread of Hours- Improve Day Spread Penalty Calculation for Multiple Shifts To ensure that penalty pay is applied only once per day to the last shift exceeding 10 hours. |
Add Max Consecutive Days value to getEmpAvailabilityV2 () response The getEmpAvailabilityV2 API now values for the Maximum Consecutive Days threshold. |
Release date for all features: November 7th, 2024
NYC Spread of Hours- Improve Day Spread Penalty Calculation for Multiple Shifts
- Enabled by default? - Yes
- Set up by customer admin? - No
- Enable via support ticket? - No
- Affects configuration or data? - Yes
- Roles affected: - T&A customers located in NYC.
What's Changing?
The Day Spread Penalty calculation will now apply oncer per day to the last valid shift that exceeds 10 hours, aligning with NYC's Spread of Hours regulation. If an employee's total spread exceeds 10 hours, the penalty pay will be added to the last shift that caused the threshold to be reached, ensuring no multiple penalties are assigned for the same day.
Reason for the Change
To enhance payroll accuracy by ensuring employees receive correct penalty pay without overcompensation for multiple shorter shifts.
Customers Affected
Time and Attendance customers located in New York.
Release Note Info/Steps
To review this enhancement:
- Navigate to Home> Staff> Punch Records.
- Confirm that "Other Pay" reflects the penalty pay only once per day for employees with shifts exceeding the 10-hour spread.
- This adjustment is also visible in the HS Payroll Report under other pay entries.
Add Max Consecutive Days value to getEmpAvailabilityV2() response
- Enabled by default? - Yes
- Set up by customer admin? - No
- Enable via support ticket? - No
- Affects configuration or data? - Yes
- Roles affected: - Customers leveraging getEmpAvailabilityV2 API
What's Changing?
The getEmpAvailabilityV2 API response has been updated to incorporate values for the Maximum Consecutive Days threshold, found in com.tdr3.hshsconnect.file.employee.EmpService.
Reason for the Change
This change is essential for users who need a comprehensive understanding of employee availability when using the Maximum Consecutive Days threshold, providing them with full access to availability data nad ensuring compliance with scheduling limitations.
Customers Affected
Customers leveraging getEmpAvailabilityV2 API.
Release Note Info/Steps
To use this enhancement, users accessing employee availability via the get EmpVailabilityV2 API will now see the Maximum Consecutive Days threshold included in their response data. This update requires no additional setup but will automatically extend data visibility within the API response.
Comments
0 comments
Please sign in to leave a comment.