Vacation Bidding – Enforce Max Employees Off

• What – Vacation bidding now enforces a strict cap on how many unique employees can select the same bid date, matching the configured Max Employees Off value and updating the OVERALL VIEW count accurately at the time of selection.
• Why – This was implemented due to customer request to prevent bid periods from allowing more employees to select a date than the department’s configured staffing minimums permit.
• How
  • Navigate to Scheduling → Time Off → Vacation Bid.
  • Ensure the bid period is configured with Max Employees Off.

 

• As employees select dates, the system validates each selection in real time against the configured maximum.
• If the limit has been reached, the system blocks the selection and displays an error message.
• Use Case – During a bid period with Max Employees Off set to 3, the fourth employee attempting to select the same date is stopped immediately, ensuring the bid board reflects the true limit and preventing downstream conflicts.
  

Vacation Bid – Submission Freeze and Timer Accuracy

• What – Vacation Bid submissions now complete successfully without getting stuck in an infinite loading state, and the bid timer now correctly pauses and preserves remaining time during status changes such as manual pauses, calling hours, and hold/stall states.
• Why – This was implemented due to customer request after bid periods were disrupted by stalled submissions, skipped users, and inaccurate timers that reduced or eliminated user bidding time.
• How
  • Navigate to Scheduling → Time Off → Vacation Bid.
  • When your bidding window becomes active, select your desired dates and click Submit.
  • The system processes the submission and advances the queue properly.
  • The timer decrements only while bid status is Active and preserves remaining time through any pause/hold state.
• Use Case – In a bid period that is paused for calling hours, users resume with the exact time they had remaining before the pause, and submissions finalize cleanly so the next bidder is not delayed.
  

Call Shift Rules – Tie Breaker Styling Restored

• What – The Call Shift tie breaker interface now displays with correct alignment, spacing, and application styling, restoring consistent visual hierarchy and preventing browser-default rendering from degrading the edit experience.
• Why – This was implemented due to customer request to ensure call shift rule configuration screens remain readable and consistent with the rest of the scheduling UI.
• How
  • Navigate to Scheduling → Call Shift Rules.
  • Click the Edit (pencil) icon on a rule.
  • Open the Tie Breaker section (shown when multiple users have equal priority).
  • The tie breaker fields and controls now display with consistent formatting automatically.

• Use Case – An admin editing tie breaker settings can clearly review and adjust the configured options without misaligned buttons or hard-to-read sections.

My Shifts – Availability Allowed with Approved Time Off When Configured

• What – Users can now mark themselves available on My Shifts even when they have approved Time Off, as long as the system configuration allows overlaps, preventing false validation errors that previously blocked availability creation.
• Why – This was implemented due to customer request to ensure availability workflows honor configured overlap rules and time off inclusion settings.
• How
  • Confirm the Time Off type has Include in Call Shift enabled in Time Off Type configuration.
  • Confirm Allow user shift overlap is enabled in Time Off Settings.
  • Navigate to Scheduling → My Shifts.
  • Select the date and click Set as Available.
    

• Use Case – A user with approved time off that is configured to be included in call shift can still indicate availability for coverage opportunities on that date when department policy allows overlaps.

Bug Fixes

Time Clock Review – Downloads No Longer Export Empty Files

• What – Downloading from the Time Clock Review table now exports the data shown on screen instead of generating empty files, restoring reliable reporting for payroll and audit workflows.
• Why – This was implemented due to customer request after teams were unable to extract time clock records for offline review despite seeing valid data in the UI.
• How
  • Navigate to Time Clock → Review.
  • Verify records are visible in the table.
  • Click the table Download/Export action.
  • Open the downloaded file to confirm the table rows and columns are included.
• Use Case – A supervisor can export the Time Clock Review table for a pay period and provide a complete report to payroll without having to rebuild the data manually.

Shift Trades – Approvers Can Approve Even If They Have Their Own Trade That Day

• What – Shift trade approval validation now correctly distinguishes between being a trade participant and being an approver, preventing approvers from being blocked by the “already accepted a trade” message when approving other users’ trades on the same date.
• Why – This was implemented due to customer request to ensure approvers can complete approval responsibilities without unrelated personal trade activity interfering.
• How
  • Navigate to Scheduling → Shift Trades (or the trade approval area used by your organization).
  • Open a pending trade request requiring approval.
  • Approve the trade; the system now evaluates approver role separately from any trades where the approver is a participant.
• Use Case – An officer who has an approved trade for the day can still approve a separate trade between two other members without being blocked by erroneous role-based validation.

Time Clock – Apparatus Display Consistency Between Clock In and Clock Out

• What – Clock Out records now display the correct apparatus value that matches the associated Clock In record, eliminating mismatched apparatus values caused by frontend rendering issues.
• Why – This was implemented due to customer request to prevent confusion when reviewing incident time tracking records for operational and reporting accuracy.
• How
  • Navigate to an incident with time clock records.
  • Review the user’s Clock In and Clock Out entries.
  • The apparatus displayed for Clock Out now reflects the stored apparatus for the record consistently.
• Use Case – A timekeeper auditing incident time can confirm the apparatus assignment is consistent across the full work session without second-guessing which unit the member was recorded on.

Mandatory Ranking – Last Updated Timestamp Respects Client Time Zone

• What – The Last Updated column in Mandatory Ranking now displays timestamps according to the client’s configured time zone, ensuring ranking actions reflect the correct local time.
• Why – This was implemented due to customer request after ranking actions appeared several hours off, causing confusion during candidate movement and mandatory fill workflows.
• How
  • Navigate to Scheduling → Mandatory Ranking.
  • Perform ranking actions (move candidates, create fills, adjust positions).
  • Review Last Updated; timestamps now align with the client-configured time zone automatically.
• Use Case – A department operating in Mountain Time can trust that ranking actions show the correct local time for audit and operational review.

Holiday Builder – Queue Processing Handles Missing Time Off Type in Buffer Validation

• What – Holiday time off generation no longer fails when buffer validation encounters missing or invalid time off type references, preventing processing errors that previously halted holiday time off creation.
• Why – This was implemented due to customer request after automated holiday processing failed during queue execution and prevented holiday time offs from being generated.
• How
  • Ensure Holiday Builder rules are configured as normal.
  • Run scheduled holiday processing; the system now validates required time off type data before buffer checks.
  • If an edge case is encountered, processing continues without stopping the entire queue.
• Use Case – During holiday auto-assignment, the system can continue creating valid holiday time offs even if one configuration edge case would have previously crashed processing.

Holiday Builder – Console Command Work Type Updates No Longer Fail

• What – The Holiday Builder console command that processes holiday shift updates now runs correctly in a console context, preventing crashes that previously blocked Work Type updates for holiday shift processing.
• Why – This was implemented due to customer request to stabilize automated holiday processing so scheduled updates complete without web-session dependencies.
• How
  • Use Holiday Builder as normal; no configuration changes are required.
  • Scheduled processing runs via console/cron and updates holiday Work Shifts reliably.
  • Queued items complete successfully instead of failing mid-run.
• Use Case – A department relying on automated holiday shift processing can trust Work Type updates apply consistently without requiring manual intervention after a queue failure.

AWT Assignments – Last Occurrence Can Be Updated Without Save Errors

• What – Assignments without time requirements (AWT) can now save updates to Last Occurrence successfully, resolving errors that prevented end-date management after users were assigned via the Shift Board.
• Why – This was implemented due to customer request to ensure AWT assignments can be ended cleanly without blocking save failures that impact schedule accuracy.
• How
  • Navigate to Scheduling → Set Up → Assignments.
  • Edit an assignment with Require Start and End Time disabled.
  • Update Last Occurrence to the appropriate date.
  • Click Save and confirm the date persists after refresh.
• Use Case – An admin can end an ongoing AWT assignment series by setting a Last Occurrence date, preventing future unintended scheduling without recreating the assignment.

AI Movement – Supports Compound Rotations

• What – AI Movement can now successfully execute movements for employees assigned to compound rotations, removing errors that previously prevented movement completion for these users.
• Why – This was implemented due to customer request to ensure automated movement recommendations can be applied consistently across all rotation types.
• How
  • Confirm permissions are enabled in Scheduling → Set Up → Automation → Enable Manual Automation.
  • Navigate to Scheduling → Shift Board and open the vacancy movement workflow.
  • Review recommendations and execute Move Employee; compound rotation users now complete successfully.
• Use Case – When a vacancy occurs, AI Movement can move an eligible member on a compound rotation into the open assignment without failing, preserving automation value for more complex rotation structures.