Categories
Share On
January 2024
Updates to the admin portal this month include integration with Hella APCs, vehicles now support Hella APC device assignment
Updates to the admin portal this month include integration with Hella APCs, vehicles now support Hella APC device assignment and display APC counts in the ridership report.
Our latest On Demand update includes the implementation of Rider Cancellation Reasons. Now, when a rider cancels their on-demand pick-up, they must select one of four provided reasons OR use the existing free-form text entry to provide a cancellation reason, in the rider app. This is different from the current workflow where a user can leave the reason blank. The provided reasons are:
- Driver is late
- I've had a change in plans
- Booking error
- Other
Dispatchers using the admin web to cancel an on-demand ride will also need to provide a reason. With these added classifications operations will now be able to efficiently categorize and analyze all ride cancellations.
Read on for details on the product enhancements we have to share this month.
iOS Updates
Rider App - 2024-01-07
New
- OnDemand | Rider Cancellation Reasons. In efforts to improve reporting, we are adding the ability to select “pre-canned” cancellation reasons.
Android Updates
Rider App - 2024-01-07
New
- OnDemand | Rider Cancellation Reasons. In efforts to improve reporting, we are adding the ability to select “pre-canned” cancellation reasons.
Rider App - 2024-01-17
Fix
- [Android TSR Stage]: Rider is unable to add Pickup notes while requesting OnDemand ride. Correcting behavior to now allow Pickup Notes entry.
Web Updates
Admin Web - 2024-01-07
Fix
- Function 'buildDistanceAndRuns' causes excessive memory consumption and performance issues. This is a backend-driven ticket to correct database issues related to memory and performance. This will not be felt by end users.
- Here polyline decoder is too slow for large polylines. This is a backend-driven ticket to correct an issue felt with excessive load times in the RideMonitor. This will not be felt by end users.
Admin Web - 2024-01-17
New
- Hella APC Integration. Vehicles now support hella apc device assignment and display apc counts in the ridership report.
- Track car seats as a capacity type for On Demand requests. We have added in car seats as a capacity type for On Demand requests. This will only show up in the admin web. This is not available in the rider app yet. We will be adding in a flag to control whether car seats should be displayed in the rider app, similar to how bikes function. To use car seats you will also need to add in the car seat capacity in vehicles. There is a 1:1 ratio between car seats and ambulatory seats, this means that a car seat will take the place of the ambulatory seat.
Improve
- Enable the CanManageInstance right for tsadmin locally. This is a backend-driven ticket to improve Instance Management settings locally for Developer usage.
- Add v2/commuteJournalChange to API doc. Updating documentation.
- Add field "Wallet User Group" under Resources > User. This is to track the ability for users to create and update Wallet User Groups throughout the TripShot Admin Console.
- Update New Rider Sign-up email template. Support HTML emails for signup, recover password and recover password via signup flow using updated new rider signup email template.
- Suppress all emails for users of an instance. Request to suppress all emails from TripShot. Instance level flag that suppresses all emails implemented into instance management.
- Suppress Wallet email for any charges that are zero dollar. By Default for all instances moving forward- no emails should be sent if the user has a zero dollar trip. To enable sending emails with zero dollar trips - the Instance Manager should have a setting to send emails.
- Store badge configuration and return as part of device mobile boot data. In efforts to work with new badge readers, we will store badge configuration info in our system.
- Add usbDevices property to "full" vehicle status JSON. This is a backend-driven ticket to incorporate USB device activity into the TripShot database. This will not be felt by end users.
- Support wallet group updates when `creating/updating` users. This is to track Wallet User Group assignment in the Resources tab. Now when updating a user’s information, the Wallet User Group for that user can be updated within the User Editor screen.
Fix
- Fix OrderedMap hashcode. This is a backend-driven ticket and will not be felt by end users.
- Function 'buildDistanceAndRuns' causes excessive memory consumption and performance issues. Work to improve efficiency and performance.
- [TSR Stage][Specific]: Error message (502) appears on searching a trip on 'Trip Planner' page. Fixes error with a minor change that eliminates commute plan candidates that start before midnight on the requested day.
- [Stage-a2]: 'Estimated MPG' (full field name) instead of 'MPG should be displayed in validation related to 'Estimated MPG' field on 'Resources >> Vehicles' page. This is to correct a cosmetic issue within the Resources > Vehicles tab in the Admin Console. Now when the Fuel Type and Estimated Miles Per Gallon options within this tab have been selected / populated and saved, the correct verbiage will be displayed at the top of the editor.
- The fixed route dashboard shows inactive routes when only the active routes is selected. This ticket is to correct an issue felt while having the ‘active routes’ selected in Fixed Route Dashboard. Now when this selection is made, only active routes will be displayed rather than both active and inactive routes.
- [Stage-a2]: Error page displayed when dispatcher/Vendor manager navigates to 'Resources >> Users' page. This is to correct an error displayed in the Resources > Users tab while logged in as a Dispatcher / Vendor Manager. This was experienced internally and not reported by end users.
- [Stage-a2]: Deleted wallet user group should not be displayed as option on 'Resources>> Users' page for consistency. This is to correct an issue felt when creating / updating a user’s Wallet Group. Previously, deleted Wallet User Groups were being displayed in this dropdown within the Resources > Users tab, but not within the Change Group editor within the Wallet tab. With this update, the deleted Wallet User Groups will be hidden from both editors.
- [Stage-a2]: Rule to set user wallet under Setting>>Rules overrides the user's wallet selected while creating a new user under Resources>>Users page. This is to correct an issue felt when creating new users within the Resources > Users tab in the Admin Console when there are Wallet Rules set within the Settings > Rules tab. Now when new users are created, their Wallet User Group will not be overridden by Rules not applied to new users.
- [Stage-a2]: No email is received when the rider purchases a pass of more than $0.00 (say $30.00) using a credit card on 'Wallet >> Passes' page. Fixes the issue of not receiving an email when the rider purchases a pass of more than $0.00 using a credit card on ‘Wallet >> Passes’ page.
- VehicleUsage job occasionally starts a TX and doesn't appear to finish (or is extremely slow). This is a backend-driven ticket to add debugging as well as updating the backend to begin travel distance calculations before starting vehicle usage transactions. This will not be felt by end users.
Beta
- Valet | Region Should be Required for a Service. Backend change to require region when creating a service.
- Valet | Update clients to use /v2/valet/keybox API. With the implementation of soft deletion of keyboxes, it was required to deliver a new version of the keybox api. The clients: admin and mobile app have now been switched to the new version of the api.
Admin Web - 2024-01-29
New
- Allow users to update and retrieve their own phone numbers (backend and web). Backend now supports Admin Web to allow users to update phone numbers; Mobile Phone Number and Home Phone Number
Improve
- Represent looping routes correctly in GTFS (With GTFS-RT updates)). Updates GTFS to comply with GTFS spec with relation to looping routes. Updates made to V2. Existing customers not impacted.
- Log all Optibus import errors to the debug log. Add Optibus errors to debug log for easier inspection.
- Run 'dismissAlerts' job once a day per instance at approximately 1AM Pacific time. Temporary solution to increased alert noise, by changing the job to run once a day during a low activity period.
- Record ETA updates in Journey Events. Investigating arrival times for Anaheim Fixed Route Vehicles require additional logging by recording ETA updates in journey events.
- Add feed_info.txt to GTFS static export. Adds feed_info.txt. to TripShots GTFS static feeds. Including feed info is a best practice and part of the California Minimum GTFS Guidelines. It's useful for both versioning and ensuring that data consumers have a good technical contact for the feed.
- Update `Explicit Wallet User Group` verbiage and make it unchecked by default. Updates verbiage; formerly “Explicit Wallet User Group” to “Override Wallet User Group” and disabled by default.
- When there are too many Optibus import errors the modal gets pushed down below the screen. Fixes an issue where import errors were not completely visible. Adds scrollbar for viewing results.
Fix
- Strip whitespace in tags before 'createMissingTags'. Fixes an issue where a duplicate error is being thrown due to differing surrounding white space.
- [Stage-a2]: 'Passenger Capacity' (Full field name) instead of 'capacity' should be displayed in the validation when admin attempts to save a Vehicle without 'Passenger Capacity' on 'Resources>> Vehicles' page. Adds error description when saving a vehicle without a valid capacity.
- [Stage-a2]: Error page displayed when Vendor manager navigates to the 'Account' page. Fixes error page displayed when Vendor manager navigates to the 'Account' page.
- [Stage-a2]: Error page displayed when admin attempts to save 'Mobile Phone Number/Home Phone Number' with more than 100 characters on 'Account' page. Fixes error when more than 100 characters are input to “Mobile Phone Number/Home Phone Number” fields.
Beta
- Valet | Ticket createdAt should be stored in DB and not generated from Events. Valet - Search function on front end utilizing events is not scalable. createdAt to be stored in DB.
- Valet | Ticket finishedAt should be either removed completely or modified as createdAt. Valet - Related to #7968, removes finishedAt field.
- Valet | Ticket.search function to filter, order and limit createdAt and finishedAt by columns rather in memory. Improved solution to increase performance when searching for tickets.
Rider Web - 2024-01-29
Improve
- Allow users to update and retrieve their own phone numbers (backend and web). Backend now supports Rider Web to allow users to update phone numbers; Mobile Phone Number and Home Phone Number