App Updates:
Android: Native: 3.1.2, JS: 3.1.4
iOS: Native: 3.1.2, JS: 3.1.4
Observer/Passenger App - Confirming a booking:
The mobile app has been updated to resolve an issue some users were experiencing when trying to select the confirm button on the ‘Plan your Journey’ screen whilst making a booking. When an update was released to the app 'over the air', on occasion this caused the confirm button to be un-selectable as the device time zone could not be deciphered for the booking to proceed. A default time zone; UTC, is now used where device time zone cannot be established.
Observer/Passenger App - Waypoint Names:
The app has been updated to better display waypoint names during booking. Where a waypoint name is long, the boarding and disembarking selection list will show the first two lines of the waypoint name in preview:
Once a waypoint has been selected, the boarding or disembarking inputs will expand to accommodate and display the selected waypoint name in full:
Website Updates:
Profile Validation:
Profiles have been improved to show the information required according to the profile role. Essential information is required to maintain profiles via bulk maintenance and for any transition to use Wonde to maintain profiles.
If the profile is a passenger; the passenger profile slider is on, either an email address or External ID are required:
If the profile is non-passenger; a user with an authorisation group or an observer, an email address is required:
If the profile is an emergency contact, a phone number is required:
Route Builder:
Where a route point was added in step 4 of route builder; Add routepoints, and a user deleted the default arrival or departure time and then used back to navigate to Step 2; Schedule, if the from and/or to date was changed, the next button wouldn't allow the user to progress to Step 3. This has now been resolved.
Where a route point was added in step 4 of route builder; Add routepoints, and a user deleted the default arrival or departure time in either hh or mm and then attempted to add another routepoint, the routepoint was returned in search but couldn't be added to the route. This has now been resolved.
An incorrect error was displayed where only one route point was added in step 4 of route builder; Add routepoints, and a user deleted the default arrival or departure time in either hh or mm in the arrival or departure fields only the error shown was: The date must be a valid format. This has been amended to display: The time must be a valid format: