Hey everyone! 

We released Version 4.44.1 on Tuesday, Dec 03, 2024. This release includes some significant updates, which you can find below. Thanks, as always, for your feedback. We're always looking for new ways to improve your experience!

MAS Integration Enhancements:

#1- Driver Activation Status Sync with MAS:

Drivers marked as "Active" or "Inactive" in the system are now automatically reflected with the same status in MAS.

Real-Time Updates: Activation status changes are synced instantly, reducing manual updates and ensuring consistency.

#2- Automatic Driver Reactivation on MAS:

Previously, if a driver deactivated on MAS was assigned to a trip in TOBI, the system could not automatically reconcile the driver's status on MAS, potentially causing assignment disruptions.

Improvement: When assigning a trip to a driver in TOBI, the system now verifies the driver's status on MAS.

If the driver is found deactivated on MAS, TOBI will automatically reactivate the driver on MAS.

Impact: These enhancement eliminates manual interventions for activating or deactivating drivers and ensures successful attestations, preventing failures

Bug Fixes:

1. Resolved issue where workbook were missing Prior Authorization Numbers, even though the numbers were correctly displayed in the Booking Form.
2. Resolved an issue that prevented users from canceling trips, displaying the error message: "A technical error occurred. Please contact the administrator."
3. Resolved an issue where standing order trips were generated for excluded dates. 
4. Resolved an issue where bookings were not being generated when updating recurrence days for future dates. This was leading to missed or incorrectly processed recurrence dates.
5.  Standing Order Issues: 
   1. Previously, updates to bookings within a standing order (SO) could inadvertently create new standing orders, change booking IDs, or untag recurring routes, leading to inconsistencies and disruptions in scheduling.
   2. Fix: We have implemented enhancements to ensure that updates made to bookings within a standing order are handled correctly without affecting SO identifiers or recurring configurations.