- The app versions have been updated as below:
iOS: Native: 2.0.0, JS: 2.1.2
Android: Native: 2.0.0, JS: 2.1.2
The latest version has been released to the Android and iOS app stores and is now available to download.
Phones provided by Kura should automatically update to the new version. Tablets provided by Kura need to be scheduled for update.
iOS Zoom level - Observer App:
When an observer views a journey the map will zoom to the route, as in Android, so that users don't need to manually zoom.
I'm here reason box - Driver App:
Where drivers skip stop(s) and visit a later geo-fence the 'I'm here' box is displayed, showing the stop(s) that have been skipped. This asks the driver if they would like to advance to the current stop.
Previously the driver was asked to enter a reason and, if no reason was entered, 'no reason given' was displayed in the journey screen.
To avoid journey delay or driver frustration the reason box has now been removed.
Upgrade to expo SDK38 and Bare Workflow:
Essential update to allow continued app development and deployment. App size has also been reduced.
The splash screen has been updated to show a message where over the air updates are being made prior to load.
Disabled Passengers - Observers:
When a passenger profile is disabled via a bulk upload, any linked observers will no longer see the disabled passenger within their app.
Disabled Passengers - Drivers:
When a passenger profile was disabled via a bulk upload, drivers were still able to select disabled passenger to board or disembark in the driver app. Disabled passenger profiles are no longer shown in the passenger list.
Passenger Search - Driver App:
Passenger search is no longer case sensitive and 'fuzzy' search has been enabled so that an exact match is not required. Matches in first name and surname will be presented where there may have been an error in spelling.
Unexpected Stop and Unexpected Journey events:
All unplanned boarding or disembarking events on a journey were shown as 'unexpected'. As billing may differ for a passenger who boards or disembarks at an unexpected stop on a scheduled trip or for a passenger that boards or disembarks a trip where they aren't scheduled, new events have been created to distinguish between unexpected stop and unexpected journey:
- UNEXPECTED_PASSENGER_BOARDED_STOP: A passenger is scheduled on the trip but has boarded at a different stop to that expected
- UNEXPECTED_PASSENGER_DISEMBARKED_STOP: A passenger is scheduled on the trip but has disembarked at a different stop to that expected
- UNEXPECTED_PASSENGER_BOARDED_JOURNEY: A passenger has boarded a trip where they weren't scheduled
- UNEXPECTED_PASSENGER_DISEMBARKED_JOURNEY: A passenger has disembarked a trip where they weren't scheduled
These events will be shown in the Journey screen for all future journeys. Historical trips will continue to show the previous unexpected event.
So that existing contract configurations don't need to be changed, the unexpected stop and unexpected journey events have been mapped to the unexpected board and disembark trigger types. This will allow the existing notifications to be sent for all of the unexpected events.
The new event types will also be available in Quicksight, for future journeys, so that report queries can amended or created to account for the differing event types.
Disabled Passengers removed from scheduled trips:
When a passenger is disabled during a bulk upload, they will now automatically be removed from all of their scheduled trips, so that the capacity is freed for other passengers that may wish to book.
Removal events for the affected passenger(s) will be shown in the Bookings table, for all trip dates affected.
New Organisation Permissions:
When a new organisation was created permissions were not automatically assigned for:
REMOVE the PERSONPROFILE USER
Journey Reporting Map
New organisations will now automatically have permission for these features so that users will be able to view these if they have permission in their auth group.
Re-send Link Code where expired:
A number of Zendesk queries were received from observers where their link codes had expired before they had been used.
Where a user tries to use a link code that has expired, they will now automatically be sent a new welcome email containing a new link code. They will be notified through the link page that they will be sent a new link code if theirs has expired. This will be sent to the email address held on their profile. As usual the new code will be valid for 7 days.
User Logged into App received failure message when linking:
A number of Zendesk queries were received from observers where they had downloaded the app and created an account before receiving the welcome email. If they stayed logged into the app and then followed the link site steps on their phone, they saw an error message saying that they were not linked, although the link was successfully established.
This has now been resolved and a user logged into the app will also see the link success message, providing there are no other issues.
When searching for a waypoint, to add a routepoint to a trip, the search now sorts by closest name and closet location.
Bulk efficiency and processed date:
The bulk upload process has been improved to prevent timeouts during the loading of large data files.
The Bulk Upload dashboard (People->Bulk Uploads) now displays the date and time that a bulk upload file was processed (m/d/yyyy hh:mm:ss).
Bulk Upload failed message:
Bulk uploads where showing a failure message in the Bulk Uploads dashboard (People->Bulk Uploads) where a file was loaded with passenger information but no observer information. The load was successful and passenger profiles were created but the failure was shown as no links between passengers and observers were established.
This has been changed so that a success message is shown, reflecting that the file has been successfully processed.
Bookings table export dates:
The bookings table csv export (Bookings->Booking summary->Select required week from Export Calendar->Export) now returns add and remove events from Monday to Sunday for the week selected from the calendar.
Early Access - Reporting Card:
The Early Access label has been removed from the Reporting card on the organisation dashboard.
Node JS update:
Essential maintenance update as the previous versions support for bug fixes, security updates and performance improvements expired.