Summary
Select the release feature from the table below to be taken directly to that section of the release note.
Feature 1 | Feature 2 | Feature 3 |
Unable to Remove Job Code from Staff Member Resolved an issue where shared employees were incorrectly flagged. |
Store Unassigned Nightly from Rule Set Resolved an issue where stores were being unassigned from labor rule sets nightly due to hierarchy and API limitations. |
HS | Receiving Multiple Confirmation Email Resolved an issue where users received multiple email confirmation notifications daily due to case sensitivity in email addresses. |
Feature 4 | Feature 5 |
Resolved an issue causing significant delays or unresponsiveness when loading the Position(s) tab in the Scheduler. |
Unable to Copy Schedule - 500 (Internal Server Error) Resolved an issue where availability processing caused errors when an employee record was not found. |
Release date for all features: February 27th, 2025
Unable to Remove Job Code From Staff Member
Description:
The system incorrectly evaluated all job assignments for shared employees as primary, causing errors when removing job codes. This issue was observed in the RemoveJobCodeStaffTabAction process, where attempts to remove a job code resulted in errors or failed silently.
Resolution:
The process was updated to correctly identify and handle primary and non-primary job assignments, allowing job code removal for shared employees without errors.
Customers Affected
Customers using HotSchedules with Shared Employees and HS integration.
Store Unassigned Nightly from Rule Set
Description:
A defect identified where store assigned to labor rule sets were being unassigned nightly. This occurred due to a "drop-then-add" approach int he assignment process, which removed stores not included in the update payload. The issue was caused by hierarchy restrictions and API behavior during store hierarchy imports.
Resolution:
The assignment process was updated to limit the impact of the "drop-then-add" method, ensuring only stores within the updating user's hierarchy are affected. This prevents unintended removal of stores from labor rule sets.
Customers Affected
This defect impacted store using labor rule sets within complex hierarchy configurations.
HS | Receiving Multiple Confirmation Email
Description:
A defect was identified where email addresses updated via API with case changes caused the system to revert the Email_confirmed status, triggering repeated confirmation emails. This issue affected users with multiple active site assignments.
Resolution:
The system was updated to normalize email addresses by treating them as case-insensitive during updated. This ensures that email confirmation status remains consistent, preventing unnecessary notifications.
Customers Affected
The defect impacted users with multiple site assignments and email updates via API integrations.
"Position(s)" Tab Not Loading
Description:
A defect was identified where the Position(s) tab in the Scheduler prolonged load times or become unresponsive. This issue was caused by inefficient handling of labor position shift collections, leading to delays in rendering data and usability issues when adding or removing shifts.
Resolution:
The performance of the labor position shift collections was optimized, significantly reducing load times for the Position(s) tab.
Customers Affected
This defect impacted customers using the Scheduler with labor positions, particularly those with large datasets or complex configurations.
Unable to Copy Schedule- 500 (Internal Server Error)
Description:
A defect was identified where the system attempted to process availability for employees who were not found in the database, resulting in errors during scheduling operations. This issue impacted the reliability of schedule copying and other related processes.
Resolution:
The system was updated to skip availability processing for employees not found in the database, ensuring smoother scheduling operations and preventing unnecessary errors.
Customers Affected
This defect impacted customers using scheduling feature where employee availability processing was required.
Comments
0 comments
Please sign in to leave a comment.