- The app versions remain the same:
iOS: Native: 1.7.0, JS: 1.7.1-101019
Android: Native: 1.6.0, JS: 1.7.1-101019
The following changes have made to the app in the last two weeks:
- Updates to all app services
- Enabling Apple NFC scanning
- A confirmation to board passengers that aren't scheduled on a trip
- Trip name display on mobile devices
- Distinguishing stop name and address
Testing is in progress and it is expected that these will be released in the next two weeks.
Reporting - Map:
You will see an 'eye' icon at the top left of the map. This allows you to hide or show journeys on the map, so that you can select only the journeys that you wish to view.
The line view has been updated to correctly reflect journey events.
The map will zoom to vehicle location, for journeys that are active for the selected date and time period.
If you are a multi-organisation user, events are cleared when you move between organisations.
Notifications Micro Service:
Our notification provider has experienced significant issues in the last week, causing a number of notifications to be delayed. The provider is working to correct the issues but, as we are aware that delayed notifications will cause confusion, a new notification service has been introduced. This will attempt to send notifications three times before discarding, providing a higher delivery success rate and preventing late notifications from being sent.
Passengers can be added to a trip if capacity is available from the stops selected. For example, where a passenger is scheduled to disembark mid-journey, capacity would be freed from this point to allow another passenger to be scheduled to board.
Person Schedule Calendar:
Occasionally a person's schedule calendar wouldn't display a trip that they were scheduled on. We have slowed down the building of the code, to reduce the quantity of requests made at once, so that all requests are captured.
Bookings were occasionally timing out resulting in a small number of requests not being made successfully. The timeouts have been extended and any unsuccessful events will be re-tried.
Code has been optimised to allow suppliers to be assigned to trips created over a long period, with a 3 year schedule limit.
Notifications from the Journey Screen:
Permissions have been updated to allow notifications to be sent from the journey screen for all user levels that have permission to view journey.
When a supplier was assigned to a schedule, that had no existing exclusion dates, an automatic exclusion date of 01/01/1970 was being added. This has now been resolved so that no dates are added unless these are requested.
Entries for notifications were showing 'Enum' after the Notification Template text. The Enum text has now been removed.