Dashboard Release Notes
Release 100, January 11, 2024
Update Details Video
Update Screenshots
[!INFO]
Developer Technical Details
Dashboard's trip event admin bug and improvements:
Remove "Not Central Time" pop up alert.
Fixed bug where line item error stops processing and retention of following line items.
Fixed bug where locations where not retained from data grid on error/warning.
Using Lytx GPS data, vehicle assigned to trip, and event dates, suggest location and odometer for each event. Users can move odometer to actual odometer with button click.
Reduced database noise by updating events, not deleting and recreating. Allows for better traceability of event changes, and less rows in database.
Further reduced database chatter by checking if Event table requires change of value versus blindly updating (ie, set Event.IsApproved = 1 where Event.IsApproved <> 1, instead of updating every damn time).
Reduced likelihood of creation of a stub event where those events already exist but are out of order (End event before waits would lead to creation of 2nd End, for example).
Reduced reliance on Session variables (PrePopSeq and PrePopEntry) which limited the dashboard from reviewing all event grid rows. Check all rows and save or warn user, keeping data modifications on screen. Reduces data loss and reliance on previous sub methods for correct data processing.
Added Event Table logging detail, where specific sub / method is updated on the row, for troubleshooting event updates and changes.
New Behavior
Event table populates odometer based on Lytx data where odometer is blank.
When trip is empty, stub events are created, with times and odometer default values.
Event grid checks for missing location and time prior to saving, reducing data loss potential.
Event grid is reorganized, with Event first, Date/Time, and then the Odometer / Suggested Odometer and Location / Suggested Location pairs.
Closing Comments note when the Event did not come in with GPS location. This has been in place for a month but is important to note. When this happens (about 27% of mobile events), background processes need to determine where the vehicle was at the time of the event to deduce the location.
Added OTP button to show pop-up of OTP details for given trip.
Updated map popup to show vehicle direction instead of generic pin, in order to make it easier to determine what a vehicle was doing at a given time.
Trip details include miles and minutes to pickup, to aid in event timing for missing events.
EventID (unique event locator number) is displayed in the event grid, to aid in troubleshooting. Where there are events in the grid that are not saved, a 0 is displayed to the user.
Route location displays a "-" after the location name when the location is not tied to the hub of the trip. The mobile application does not use hub to assign locations, only client. Dashboard requires the hub/client pair. This indicates a point not assigned to the hub of the trip (however a valid point).
- Dashboard is wrong in this case, as that was for limiting display options, but it's somewhat baked in for the time being. Future updates will seek to address this.
-PointOfServiceID is a tooltip on the EventID field, in order to provided additional troubleshooting details where needed.