Release Notes - Scheduling Module

Release Notes - Scheduling Module

In order to provide you with more detailed information on our updates, we have broken the Release Notes down by module. 


Enhancements

Add Ability to Edit Ranking Number

• What - Administrators can now directly edit call shift rankings by entering position numbers, providing an alternative to the drag-and-drop interface. This enhancement streamlines ranking management for large organizations by allowing precise numerical positioning without manual dragging through multiple positions while maintaining full compatibility with existing drag-and-drop functionality.

• Why - This enhancement was implemented due to customer request to provide a more efficient method for managing rankings in large organizations where dragging users through multiple positions was time-consuming and cumbersome.

• How - To use this feature:

  1. Navigate to the call shift ranking interface for your desired shift type
  2. Locate the user whose position you want to modify
  3. Click the pencil icon next to the cross hairs (drag handle) for that user
  4. Enter the desired position number using your keyboard
  5. Save the changes to apply the new ranking
  6. The system automatically moves the user to the specified position and adjusts all other users accordingly
  7. A manual adjustment indicator appears next to the repositioned user's name
  8. Note: The edit ranking icon is only displayed if the logged-in user has the Update Call Shift Rankings permission



• Use Case - A scheduling administrator managing a department with 150 employees needs to move an employee from position 145 to position 5 in the call shift ranking due to a recent certification. Instead of dragging the employee through 140 positions, the administrator simply clicks the pencil icon, types "5" in the position field, and saves the change, instantly repositioning the employee while the system automatically adjusts all affected rankings.


Call Shifts - Stop and Award

• What - This feature enables administrators to manually conclude call shifts before their scheduled deadline while maintaining the standard award process. It provides greater flexibility in shift management when suitable candidates are already available, eliminating the need to wait for automatic deadline-based awards while preserving all existing award logic and candidate evaluation criteria.

• Why - This enhancement was developed due to customer request to provide administrators with the ability to expedite the award process when qualified candidates have already responded, reducing unnecessary wait times and improving operational efficiency.

• How - To execute an early award:

  1. Access Call Shift Details by navigating to an active call shift that uses the candidate method
  2. Locate the "Stop and Award" button positioned next to the existing "Stop" button in the call shift interface
  3. Click "Stop and Award" to immediately modify the deadline to the current time
  4. The system automatically stops further candidate calls and initiates the standard award process
  5. The shift is awarded to the appropriate candidate based on existing response criteria
Prerequisites: Call shift must be configured with the candidate method, must be in active/open status with available candidates, and user must have administrative permissions to modify call shifts



• Use Case - An administrator creates a call shift for an emergency overtime position with a 4-hour deadline, but within 30 minutes, three qualified candidates have already responded and accepted. Rather than waiting the full 4 hours for the automatic award process, the administrator uses the "Stop and Award" feature to immediately close the call shift and award it to the best-qualified respondent based on the system's evaluation criteria, getting the position filled quickly.



Build New Rotation

• What - New rotation rules have been introduced to the scheduling system, offering more flexibility in shift assignments with multiple complex patterns including Windsor rotations and various on/off configurations. These patterns support diverse scheduling needs from simple alternating schedules to complex multi-week rotations that can accommodate various operational requirements.

• Why - These new rotation patterns were added due to customer request to support more diverse scheduling requirements and provide greater flexibility in creating rotation schedules that match specific operational needs.

• How - To implement new rotation patterns:

  1. Navigate to Setup → Rotations → Rules 
  2. Include the desired new rotation rules for your client account (they are excluded by default)
  3. Once included, associate the rotation rules with a rotation
  4. Apply the rotation on the Shift Board 
  5. New patterns include Windsor rotation, various on/off patterns (1 on/7 off, 2 on/40 off, etc.)
  6. These rotation patterns can also be used when adding Kelly Days based on rules to user rotations

• Use Case - A fire department needs to implement a Windsor rotation pattern for their specialized hazmat team that requires a complex 56-day cycle with varying on/off patterns. The administrator enables the Windsor rotation rule in the system settings, creates a new rotation using this pattern, and assigns it to the hazmat team members, automatically generating their schedule for the entire year based on the complex pattern without manual entry.



Add Accepted Call Shifts to My Shifts

• What - This enhancement adds visibility for accepted call shifts directly within the My Shifts interface, ensuring users can track their commitments even when shifts haven't been formally assigned yet. This addresses a critical gap where users could accept call shifts but forget about them due to lack of calendar integration until official assignment, providing complete shift information and maintaining all existing work shift functionality.

• Why - This feature was implemented due to customer request to improve visibility of accepted call shifts and prevent users from forgetting about shifts they've committed to but haven't been formally assigned yet.

• How - The feature works automatically:

  1. User accepts a call shift through the standard acceptance process
  2. System automatically displays the accepted call shift in My Shifts on the appropriate activity date
  3. Shift appears with call shift details, time frame, and associated work type
  4. Users can interact with the call shift entry using all standard My Shifts options
  5. Users can add availability preferences and view shift details
  6. If administrators remove or delete the call shift, it automatically disappears from the user's My Shifts view



• Use Case - A paramedic accepts a call shift for next Saturday's overnight coverage but the shift won't be formally assigned until Friday when all responses are collected. The accepted shift immediately appears in their My Shifts calendar view, allowing them to see their commitment alongside their regular shifts, add availability preferences if needed, and plan their week accordingly without risk of double-booking or forgetting about the accepted shift.


Time Clock - Launch Kiosk Button

• What - A new launch button has been added to the time clock history page to provide administrators with direct access to kiosk mode functionality. This enhancement eliminates the need for administrators to manually navigate to or remember specific URLs, streamlining the process of setting up shared clocking stations for employee use with one-click access from the history page.

• Why - This feature was added due to customer request to simplify the process of accessing kiosk mode for administrators who frequently need to set up shared time clock stations for employees.

• How - To access kiosk mode:

  1. Navigate to SCHEDULING → TIME CARD → TIME CLOCK HISTORY 
  2. System validates user has both kiosk launch and history view permissions
  3. Click the kiosk launch button that appears if permissions are met
  4. Kiosk interface opens, ready for employees to clock in and out



Note: Feature is restricted to desktop and iPad devices only. User must have both kiosk launch permissions and history view permissions enabled

• Use Case - A shift supervisor needs to set up a shared time clock station at the beginning of each shift for firefighters to clock in and out. Instead of bookmarking URLs or navigating through multiple menus, the supervisor simply goes to the time clock history page and clicks the launch kiosk button, instantly opening the kiosk interface on the station's iPad for employee use throughout the shift.


Add District to Call Shifts

• What - Agencies can now filter call shifts by district to ensure they contact the appropriate personnel groups when staffing assignments. This enhancement streamlines the call process by allowing organizations to target specific geographic or organizational districts with multi-select capability, integrating seamlessly with existing field management district data and maintaining consistency with current shift and rank filters.

• Why - This feature was implemented due to customer request to improve call shift targeting by allowing organizations to limit calls to specific districts, reducing unnecessary notifications to personnel outside the relevant geographic or organizational areas.

• How - To filter call shifts by district: 

  1. Navigate to SCHEDULING → SET UP → CALL SHIFT RULES → ADD RULE 
  2. Expand the "Advanced Options" section
  3. Locate the new "District" filter positioned beneath the "Shifts" filter
  4. Select one or multiple districts from the dropdown (districts are pulled from field management)
  5. The system will automatically filter to show only personnel assigned to the selected district(s)
  6. Proceed with creating the call shift as normal - only users within the specified districts will be contacted



• Use Case - A large county fire department with five distinct districts needs to fill an overtime shift at the North District station. When creating the call shift, the administrator selects only "North District" from the district filter, ensuring that only personnel assigned to the North District receive the call shift notification, preventing unnecessary calls to firefighters in the South, East, West, and Central districts who would be unlikely to accept due to distance.



Vacation Bid Callback - Continue Processing After Time Off Creation Error

• What - The vacation bid process now automatically continues when individual users encounter time off creation failures, preventing system bottlenecks and maintaining workflow continuity for all participants in the bid queue without requiring manual intervention.

• Why - This enhancement was implemented due to a customer request to eliminate delays in the vacation bid process that occurred when a single user's time off creation failed, which would halt the entire queue and require administrative intervention to resume operations.

• How - The enhanced error handling is automatically active for all vacation bid processes and requires no configuration changes.

  • Failed users are marked with visual error indicators but do not stop queue progression
  • The system automatically moves to the next user when time off creation fails
  • Error details are logged for supervisor review while maintaining user privacy
  • Manual review of failed requests may be required after bid completion

• Use Case - During a department-wide vacation bid with 50 personnel, if one user encounters a time off creation error due to insufficient balance or overlapping requests, the remaining 49 users can complete their vacation selections without delay, while supervisors can address the failed request separately after the bid process concludes.



Vacation Bid - Time Off Creation Failure Notification

• What - The system now automatically sends email notifications to users when their vacation bid requests fail to be created due to technical errors, validation failures, or system constraints, providing immediate feedback about unsuccessful submissions.

• Why - This feature was added due to customer request to ensure users receive prompt notification when their vacation requests fail, preventing users from incorrectly assuming their requests were successfully submitted.

• How - Email notifications are automatically triggered when time off creation fails and require no setup beyond ensuring users have valid email addresses in their profiles.

  • Failure detection occurs automatically during vacation bid processing
  • Notification emails are sent immediately to both users and administrators
  • Email content includes time off type, requested dates, and standard messaging
  • Users should not reply directly to automated system emails

• Use Case - When a firefighter submits a vacation bid request for dates that conflict with existing approvals or exceed their available balance, they receive an immediate email notification explaining the failure, allowing them to adjust their request promptly rather than discovering the issue days later during schedule review.



Vacation Bid - Time Off Visual Indicator for Selected Days in User Rounds

• What - Color-coded visual indicators now display for selected days in user rounds, providing immediate visibility into time off status with green indicators for successfully created time off and red indicators for failed or restricted time off creation.

• Why - This enhancement was implemented due to customer request to improve workflow efficiency by allowing administrators to quickly distinguish between successful and failed time off requests without reviewing detailed logs or individual entries.

• How - Visual indicators are automatically displayed in the vacation bid interface and update in real-time.

  • Navigate to SCHEDULING → TIME OFF → VACATION BID
  • Click on bid details to access user rounds section
  • Select a user to view their schedule with color-coded indicators
  • Green indicators show successfully created time off
  • Red indicators show failed or restricted time off creation
  • Hover over indicators for additional status context



• Use Case - During vacation bid review, an administrator can immediately identify that three out of ten requested days for a specific user failed due to staffing restrictions by viewing the red indicators, allowing for quick assessment of which requests need alternative solutions or manual intervention.



Allow Trades to be Edited

• What - Administrators can now edit trade-related time off entries after approval using the same editing capabilities available for standard time off entries, including modifications to time off type, subtype, and project codes as business needs require.

• Why - This feature was added due to customer request to ensure accurate payroll processing by providing administrators the ability to modify approved trade entries when business requirements change after initial approval.

• How - Edit functionality is available to users with appropriate permissions for approved trades.

  • Locate approved trade entry on the shift board
  • Click the edit icon next to the time off entry (visible only to authorized users)
  • Modify time off type, subtype, and/or project code in the edit modal
  • Review any time off rule warnings or accrual notifications
  • Override warnings if necessary using admin permissions
  • Save changes to update associated entries automatically




• Use Case - When an approved shift trade initially coded as regular overtime needs to be recategorized as emergency callback due to incident circumstances, an administrator can edit the trade entry to update the time off type and project code, ensuring proper payroll classification and budget tracking without reversing the entire trade process.



Time Off - Denied Time off to Original Position

• What - Users are automatically restored to their original shift positions when time off requests are denied or deleted after their position has been filled by another user, ensuring seamless workforce continuity without removing users from the shift board.

• Why - This enhancement was implemented due to customer request to prevent staffing gaps and maintain schedule integrity when time off decisions are reversed after replacement personnel have been assigned to cover positions.

• How - Position restoration occurs automatically when time off is denied or deleted and requires no manual intervention.

  • System checks position availability when time off is denied or deleted
  • If position is occupied, both original and replacement users are maintained
  • Users are placed in adjacent positions on the shift board
  • For partial time off scenarios, restored shifts are combined with original assignments
  • All standard assignment validations apply to modified schedules

• Use Case - When a paramedic's approved vacation request is denied due to emergency staffing needs after a replacement has already been scheduled, both the original paramedic and their replacement are automatically positioned adjacent to each other on the shift board, ensuring double coverage without creating scheduling conflicts or requiring manual repositioning.



Time Clock Table - Add Module to the Table

• What - Module tracking capabilities have been added to the time clock system, enabling administrators to monitor which specific modules users are clocking into across the platform with enhanced filtering and export functionality for comprehensive activity oversight.

• Why - This enhancement was implemented due to customer request to provide better visibility into user activity distribution across different system modules, supporting improved resource allocation and operational oversight for department management.

• How - Module tracking is automatically integrated into the time clock interface with new columns and filtering options.

  • Navigate to the Time Clock management interface
  • View enhanced table with new Module Type and Name columns
  • Use module filter dropdown to select specific modules (Shift Board, Incidents, Training, Events)
  • Apply search functionality to locate specific entries or users
  • Export filtered results using download feature for reporting
  • Module selection is required for all new time clock entries



• Use Case - A fire chief reviewing monthly activity reports can filter time clock data to show only training module usage, identifying which personnel are actively engaging with continuing education requirements and which departments may need additional training support or resource allocation.



Mandatory - New Ranking List

• What - The mandatory ranking table has been updated to match the modern table style and functionality already implemented in the call shift ranking page, providing administrators with consistent filtering capabilities and interface uniformity throughout the application.

• Why - This enhancement was implemented due to customer request to maintain consistent user experience across ranking systems and provide comprehensive filtering options that improve administrative efficiency in managing mandatory assignments.

• How - The updated table provides enhanced filtering and consistent design elements.

  • Access the mandatory ranking page with appropriate permissions
  • Use the filter panel to select Qualifiers (triggers loading of related Call Shift Rules)
  • Select specific Call Shift Rules based on chosen qualifier
  • Set Status filter (Available, Unavailable, Excluded)
  • Define Date range for ranking data
  • View populated table with Position, Staff Name, Current Status, Cumulative Hours, and Ranking Value
  • Drag handles allow for manual reordering of positions



• Use Case - When managing mandatory overtime assignments for a large department, an administrator can filter the ranking list by specific qualifications such as "Hazmat Certified" and date range to identify the next eligible personnel for specialized emergency response, ensuring fair rotation and appropriate skill matching for critical incidents.


Contacted and On Duty

• What - A new "Contacted and On Duty" option has been added to call shift rules that provides granular control over when users are charged for call shifts, ensuring users are only charged when they are both contacted for a call shift AND currently on duty at the exact time the shift starts.

• Why - This enhancement was implemented due to customer request to provide fairer charging logic for complex scheduling scenarios where users should only be charged when multiple specific conditions are met simultaneously, improving accuracy in shift management and billing.

• How - The new charging option is available in call shift rule configuration for both Rotation and Hourly rule types.

  • Navigate to Scheduling → Setup → Call Shift Rules
  • Create or edit an hour-based rule (Rotation or Hourly)
  • Select "Contacted and On Duty" from the "Apply hours When" dropdown
  • Configure additional rule parameters as needed
  • Save the rule for immediate implementation
  • Runtime behavior automatically validates duty status at shift start time



• Use Case - When a callback is initiated for a structure fire at 0300 hours, firefighters who are contacted but currently off-duty will not be charged callback hours unless they respond and report for duty, while those contacted who are already on-duty at 0300 hours will be automatically charged according to the configured rule, ensuring accurate compensation tracking for complex staffing scenarios.



Update Call Shift Setting - Call Shift Rotation

• What - Call shift rotation logic has been updated to honor contract requirements by rotating users to the bottom of the ranking list on the actual day of their work shift rather than when they accept the shift, ensuring proper timing for "Last Date Worked" rotational rules.

• Why - This enhancement was implemented due to customer request to align system behavior with contractual obligations that specify rotation timing based on actual work performance rather than shift acceptance, ensuring fair and compliant rotation scheduling.

• How - The enhanced rotation logic is controlled by a configurable setting that affects "Last Date Worked" rules.

  • Admin enables ROTATE WHEN THE DAY OF THE SHIFT ARRIVES setting in SCHEDULING → CALL SHIFT RULES → SETTINGS
  • For "Last Date Accepted" rules: User rotates immediately upon acceptance (unchanged behavior)
  • For "Last Date Worked" rules with setting enabled: User maintains ranking position until actual work shift date
  • On shift date morning: Users with "Last Date Worked" rules automatically rotate to bottom of ranking
  • Other users continue rotating based on their own shift completion dates



• Use Case - Under a contract requiring rotation based on actual work dates, when a firefighter accepts a callback shift on Monday for Thursday duty, they maintain their current ranking position through Wednesday, allowing other personnel to be selected for Tuesday and Wednesday callbacks, then automatically rotate to the bottom of the list on Thursday morning when their actual work shift begins.


Bug Fixes 

Incorrect Warning Message for AWT Consecutive Hours Calculation

• What - This fix resolves incorrect warning messages that were displaying when assigning users to rotation partial shifts on AWT (Assignment Without Time). The system was incorrectly calculating consecutive hours for users with gaps in their schedule, triggering false warnings about exceeding maximum consecutive hours limits even when assignments were well within configured thresholds, now ensuring accurate consecutive hour tracking across different time periods.

• Why - This fix was implemented due to customer request after users reported receiving false warning messages when making valid assignments that were incorrectly calculated as exceeding consecutive hour limits.

• How - The fix works automatically:

  1. Navigate to SCHEDULING → SET UP → SETTINGS to configure maximum consecutive hours and minimum break requirements
  2. Create rotation assignments for users with existing schedule gaps
  3. System now correctly calculates actual consecutive working hours
  4. Validates against configured thresholds before displaying warnings
  5. System recognizes schedule gaps and resets consecutive hour calculations appropriately
  6. Only triggers warnings when actual consecutive hours exceed configured maximums

• Use Case - A scheduler assigns an employee to work Monday through Thursday from 08:30 to 16:30 (8 hours per day, 32 hours total) with a configured 48-hour consecutive limit. Previously, the system would incorrectly warn about exceeding the limit despite the 32 hours being well under the 48-hour threshold. With this fix, the assignment proceeds without false warnings, correctly recognizing the actual working hours.


Shift Trades - Unassigned Shifts Ignore Trade-Specific Work Type

• What - This release addresses an issue where unassigned shifts resulting from trade requests were incorrectly inheriting the system default work type instead of the work type configured in Trade Settings. The fix ensures consistent work type application across all trade scenarios, with both assigned and unassigned shifts now following the same work type logic, improving scheduling accuracy and reducing manual corrections.

• Why - This fix was implemented due to customer request after organizations reported that traded shifts were not maintaining the correct work type, requiring manual corrections and causing confusion in scheduling.

• How - To ensure proper work type application:

  1. Configure the desired work type in Scheduling → Setup → Time Off Settings → Trade Settings → Default Option → Work Type 
  2. When an unassigned user initiates a trade request via Scheduling → MyShifts 
  3. User selects date, clicks blank space, and selects "Request Trade" 
  4. System now applies the work type from Trade Settings (not the starred default from Work Types setup)
  5. Trade proceeds through normal approval workflow
  6. Resulting shift maintains the correct work type from Trade Settings
  7. When shift is dragged to Shift Board, work type remains consistent

• Use Case - An unassigned employee requests to trade into a shift that should be designated as "Overtime" work type per the Trade Settings configuration. Previously, the system would incorrectly apply the default "Regular" work type, requiring manual correction. Now, when the trade is approved, the shift automatically maintains the "Overtime" designation throughout the entire process, from initial request through final scheduling on the Shift Board.


Assignment End Date Validation Issue

• What - This fix resolves an issue where users were unable to update assignment end dates even when no validated assignments existed after the requested end date. The system now correctly allows end date modifications when there's no risk to data integrity, while maintaining protection against validated data loss and providing clear error messaging when updates cannot proceed due to validated data conflicts.

• Why - This fix was implemented due to customer request after users reported being unnecessarily blocked from updating assignment end dates when no validated data would be affected by the change.

• How - To update assignment end dates:

  1. Ensure PREVENT DELETION OF VALIDATED DATA toggle is enabled in SCHEDULING → SET UP → SETTINGS → SHIFT BOARD SETTINGS 
  2. Navigate to SCHEDULING → SET UP → ASSIGNMENTS 
  3. Select the assignment requiring an end date update
  4. Modify the assignment end date
  5. System validates whether validated assignments exist after the proposed end date
  6. If no validated assignments exist: End date update proceeds successfully
  7. If validated assignments exist: Error message displays, preventing the update
  8. Updated end date is immediately reflected in assignment details

• Use Case - An administrator needs to end an employee's temporary assignment on March 15th instead of March 31st due to the employee returning to their regular position early. Since no validated shifts exist between March 16th and March 31st, the system now allows the administrator to update the end date to March 15th immediately, whereas previously this would have been blocked unnecessarily even without any validated data at risk.


Call Shift Not Charging Users with No Response Status When "Only Charge Above Accepting Users" is Enabled

• What - The system now properly applies Rule apply hours for users with "No Response" status when "Only charge above accepting users" is enabled, resolving a critical issue where No Response users were not being charged according to configured rules.

• Why - This fix was implemented due to customer request to ensure accurate billing and shift management across all user response types, maintaining consistent rule application regardless of response status.

• How - No configuration changes are required as the fix automatically applies to existing rule setups.

  • System evaluates all users regardless of response status during charging process
  • Users with Accepted status are charged per configured rules
  • Users with Denied status are charged per configured rules
  • Users with No Response status are now charged per No Answer rule configuration
  • Charges are applied consistently across all response types according to Rule apply hours settings

• Use Case - When a department-wide callback is initiated and several firefighters do not respond to their notification within the specified timeframe, those with No Response status will now be properly charged callback hours according to the configured No Answer rule, ensuring consistent policy enforcement and accurate payroll processing for all personnel regardless of their response behavior.



Unassigned disallowing switch of employees

• What - An error preventing users from switching partial shifts when the same user appears on both the Shift Board and Unassigned Person list simultaneously has been resolved, eliminating the "Unassigned person time range" error that was blocking essential scheduling operations.

• Why - This fix was implemented due to customer request to resolve scheduling conflicts that prevented proper user switching operations when personnel had split scheduling status between assigned and unassigned time periods.

• How - The enhanced validation logic automatically resolves time range conflicts without requiring configuration changes.

  • Navigate to Scheduling module and access the Shift Board
  • Select "Switch User" function for any partial shift assignment
  • Choose replacement user from available options
  • System validates time ranges across both Shift Board and Unassigned Person contexts
  • Switch completes without validation errors
  • Both Shift Board and Unassigned Person list update to reflect changes automatically

• Use Case - When attempting to replace a firefighter who has a partial shift assignment (0800-2000 on active duty, 2000-0800 on unassigned status), administrators can now successfully complete the user switch operation without encountering time range validation errors, allowing proper coverage adjustments for personnel availability changes.



Shift Trade Time Off Overlap Issue

• What - The system now properly respects "Allow User Shift Overlap" settings in conjunction with work type "Is Shift" configuration, resolving an issue where legitimate shift trades were incorrectly prevented when one user had Time Off.

• Why - This fix was implemented due to customer request to eliminate false overlap warnings that blocked valid trades between users when appropriate configuration settings should have allowed the transactions to proceed.

• How - The fix automatically applies to existing configurations without requiring changes to current settings.

  • Ensure "Allow User Shift Overlap" is enabled in Scheduling → Setup → TIME OFF settings → TIME OFF SETTINGS
  • Verify work type has "Is Shift" option set to OFF (default setting)
  • Navigate to shift trading functionality as usual
  • Select shift to trade with user who has Time Off on the same date
  • System evaluates overlap conditions and proceeds without false conflict messages
  • Trade completes successfully when settings allow overlap

• Use Case - When a paramedic needs to trade their Thursday shift with a colleague who has scheduled vacation time off on Thursday, the trade can now proceed successfully if the department has enabled shift overlap settings, allowing both personnel to accommodate their scheduling needs without administrative intervention or false system conflicts.



• What - Duplicate user entries in Add Trade search functionality have been eliminated when users have multiple roles assigned, ensuring each user appears only once in search results for improved user experience and reduced administrative confusion.

• Why - This fix was implemented due to customer request to resolve search result confusion that occurred when personnel with multiple departmental roles appeared multiple times in trade assignment searches, complicating the selection process.

• How - Search result deduplication is automatically applied without affecting existing Add Trade workflow or functionality.

  • Navigate to Shift Board as usual
  • Right-click on any user's shift and select "Add Trade"
  • Begin typing user's name in the search bar
  • Users with multiple roles now appear only once in dropdown results
  • Select desired user and proceed with trade creation normally
  • All existing Add Trade features and workflows remain unchanged

• Use Case - When creating a shift trade and searching for a firefighter who serves in multiple roles such as both apparatus operator and rescue technician, they will now appear only once in the search results instead of multiple duplicate entries, allowing administrators to quickly locate and select the correct personnel for trade assignments.



Import Wizard Queue User Data Issue

• What - A critical issue where the import wizard failed to process jobs through the queue system due to missing user session context has been resolved, ensuring user data is properly passed to queue jobs while maintaining performance benefits of the queue-based architecture.

• Why - This fix was implemented due to customer request to restore import wizard functionality that was affected by architectural improvements to queue-based processing, ensuring reliable data import operations for ongoing system use.

• How - The resolution automatically preserves user context during import processing without requiring configuration changes.

  • Navigate to import wizard as normal
  • Initiate import process requiring user data
  • System captures and packages necessary user context automatically
  • Import job submits to queue with user data included in job payload
  • Queue processors access user data directly from payload instead of session
  • Import process completes successfully without console errors

• Use Case - When a fire department administrator uploads monthly personnel data through the import wizard, the system now successfully processes the import job through the queue system with proper user permissions and context, ensuring data integrity and completion without the technical errors that previously interrupted bulk data operations.



Kelly Days Removal When Setting Rotation "Until" Date

• What - A critical scheduling bug has been resolved where setting an "Until" date on user rotations with Kelly days incorrectly removed past Kelly day assignments and caused position overlaps, ensuring validated assignments are preserved and scheduling conflicts are prevented.

• Why - This fix was implemented due to customer request to maintain scheduling integrity when rotation end dates are applied, preventing the loss of previously approved Kelly day assignments and eliminating position conflicts that disrupted established schedules.

• How - Assignment preservation occurs automatically when applying rotation end dates without requiring manual intervention.

  • Create rotation with Kelly days configuration (e.g., every 5 shifts)
  • Allow Kelly days to be validated and assigned in the system
  • When applying "Until" date to the rotation, system preserves existing assignments
  • System checks for Kelly day assignments prior to end date and maintains them
  • Prevents reassignment to positions already occupied by other users
  • Maintains scheduling integrity without creating overlaps or conflicts

• Use Case - When ending a firefighter's rotation pattern that included Kelly days every fifth shift, previously scheduled Kelly days remain in both the Time Off system and Shift Board, while positions filled by replacement personnel during those Kelly days stay intact, preventing double-booking and maintaining the validated schedule structure that departments rely on for consistent staffing coverage.

    • Related Articles

    • Mobile App: Release Notes (May 2025)

      In order to provide you with more detailed information on our updates we have broken the Release Notes down by module. Video Current iOS Version 5.8.4 Current Android Version 6.9.4 New Features (iOS) Fire Investigations Menu Integration What: Fire ...

    • Release Notes - Scheduling Module

      In order to provide you with more detailed information on our updates we have broken the Release Notes down by module. New Features 1. View Ranking Permission We have added a new permission "Scheduling - Call Shifts - Edit Only Own Ranking. This will ...

    • Release Notes - Scheduling Module

      In order to provide you with more detailed information on our updates, we have broken the Release Notes down by module. Feature Enhancements Cloning of Vacation Bids What: You can now clone vacation bids. Why: This was done to improve your experience ...

    • Release Notes - Scheduling Module

      In order to provide you with more detailed information on our updates we have broken the Release Notes down by module. Feature Enhancements Qualifiers can be used multiple times. What: You are now able to use Qualifiers across multiple Call Shift ...

    • Release Notes - Scheduling Module

      In order to provide you with more detailed information on our updates, we have broken the Release Notes down by module. Enhancements Off Roster and Accrued Time Off Update What - This enhancement enables immediate processing of work type-based ...