bug fixes

Resolved issues associated with default settings for the mdt-api server (Production vs. Dev). Corrected an issue preventing successful logout due to a missing sessionID. Reduced the spacing between entries in the Trip Modifications notification to increase the amount of viewable information as a short-term fix to challenges displaying larger amounts of information. Disabled the configuration to display the ‘notify’ button - exclusively used by Parascope. Modified the Trip Modifications notification when pickup priority is changed to Dropoff priority to only show the updated dropoff time. cImproved the trip modification notification to show “and Dropoff” in order to remove any uncertainty when a new trip is added. Improved the Trip Modification notification to include “and Dropoff” to eliminate possible driver confusion. Resolved issues with Trip Modifications notifications for Will Call priority trips so they will show Pickup and Dropoff and reference the time of the trip. Corrected the Trip Modifications notifications for Priority Will Call trips that are removed so they show both Pickup and Dropoff and include the time of the trip. Introduced changes to the “Start Route” button to insure it is properly enabled for use. Made improvements to update to the information displayed in notifications in the Driver App when changes have been made on Pickups and/or Dropoffs. Corrected issues with trip modification notifications causing the notification to include trips that were not modified. Made improvement to the notifications shown on the Driver App when a trip is removed. Removed an errant space displayed in times when update notifications are shown on the Driver App. Corrected issues preventing users from accessing the full list of options in the No Show reason screen. Introduced a requirement on the Driver App that Location Services must be enabled in order to use the App. This is required to properly calculate distances traveled and automatically update the odometer calculations. Improved state handling of information presented to drivers before and after login - so that Trip Modification notifications and Pre-trip inspection are not shown until a driver successfully authenticates in the application. Resolved issues causing the Ecolane Driver app to free when attempting to update odometer meter readings. Introduced UX improvements for stops with multiple pickups / dropoffs (Group Trips) for drivers managing the boarding/unboarding process.

Ecolane has made significant investments in the communication layer between Ecolane Evolution and Ecolane Driver. These improvements include: Improved Communication Protocols: Enhanced Real-time Communication: Ecolane Driver now employs advanced communication protocols to facilitate seamless, real-time communication between drivers and the dispatching system. This ensures that ride requests, updates, and notifications are delivered promptly and accurately. Improved Two-Way Communication: The platform supports two-way communication channels, allowing drivers and dispatchers to exchange messages, updates, and requests as needed. This fosters clear and efficient communication, leading to smoother ride experiences for all parties involved. New Redundancy and Failover Mechanisms: Ecolane Driver incorporates redundancy and failover mechanisms within its communication protocols to ensure reliability and continuity of service, even in the event of network disruptions or server failures. Enhanced Stability: New Fault-Tolerant Architecture: Ecolane Driver has been redesigned with a fault-tolerant architecture that minimizes the impact of system failures or errors. Expanded Error Handling and Recovery: The platform includes robust error handling and recovery mechanisms to detect, diagnose, and recover from errors quickly and efficiently. This helps maintain system stability and prevents disruptions to service. New Load Balancing: Ecolane Driver leverages a new framework utilizing load balancing techniques to distribute incoming traffic evenly across servers and resources. This ensures optimal performance and prevents overload situations that could compromise system stability. Improved Scalability: New Elastic Infrastructure: Ecolane Driver leverages elastic infrastructure capabilities to dynamically scale its resources based on demand. This allows the platform to seamlessly accommodate fluctuations in user activity, such as increased ride requests during peak hours or in high-traffic areas. New Horizontal Scaling: The platform supports horizontal scaling, allowing additional servers and resources to be added to the system horizontally as needed. This ensures that the Ecolane Driver service can scale to support growing user bases and expanding service areas without sacrificing performance or reliability. New Distributed Architecture: Ecolane driver leverages a distributed architecture that enables scalability across geographically distributed locations. This allows the platform to efficiently serve users in different regions while maintaining consistent performance and reliability.