- The app versions have been updated as below:
iOS: Native: 2.1.0, JS: 2.2.0
Android: Native: 2.1.0, JS: 2.2.0
The latest version has been released to the Android and iOS app stores and we expect this to be available to download by the 21st October 2020
Phones provided by Kura should automatically update to the new version. Tablets provided by Kura need to be scheduled for update.
Potential Breaking Change
As Terms and conditions is a new feature, it also requires the minimum version of the app listed above. We suggest that T&C's are not enabled for any organisation until the vast majority of devices have updated. Our recommendation is to not apply terms and conditions to any contract until at least 30 November 2020. If terms and conditions are applied, then any users of an older version of the mobile app will receive a booking failed message when booking, this can be resolved by updating to the latest app version.
In App Booking Terms and Conditions:
Booking Terms and Conditions (T&Cs) will be shown in the app where an observer selects to book a trip that has a T&Cs PDF available in the associated contract (please see the website section below for contract configuration information).
On the Select Dates screen, observers will be asked to confirm that they accept the Booking T&Cs. Until these are accepted the BOOK button can't be selected.
If they select the 'booking T&Cs' hyperlink this will open a window where the T&Cs can be viewed.
Once they have moved the slider to the right to accept, the BOOK button will highlight in Kura pink and can be selected.
When an observer books in future they will be shown a link to 'View accepted booking T&Cs' that they can select to view the accepted T&Cs.
Booking T&Cs apply at a contract level so, once an observer has accepted the T&Cs for a contract, the acceptance will apply to all of their passengers, for any trip that is set-up under that contract.
If no T&Cs are available for a contract then observers will be able to proceed with booking as normal, without needing to accept T&Cs.
If a T&Cs are replaced for a contract, then observers will be asked to accept the new T&Cs when they next book.
BG Location Update:
Location and geo-fence services have been updated to the latest version, to ensure full compatibility for iOS 14 and Android 11.
Expo SDK 39:
To allow support for future app releases, the latest version of Expo framework has been implemented.
Booking Terms and Conditions - Contract configuration:
The Contracts summary page has changed to allow Booking Terms and Conditions (T&Cs) to be loaded to contracts. There are now separate areas for rule and T&Cs configuration.
- If you select VIEW RULES you can view any alarms or notifications configured and see what searchable by (for in app booking) is set to.
- If you select EDIT RULES, you can administer alarms, notifications and searchable by (for in app booking to made active/inactive).
You can load booking T&Cs to a contract by selecting EDIT BOOKING T&Cs.
This will open a page where you can drag and drop a PDF, or select to browse to a location on your computer to attach a PDF. When dragging and dropping a PDF you will see '+COPY' when this has been recognised and can be dropped.
Once you have dragged and dropped the PDF or have selected this from a computer location, you will see an attachment icon in the upload box and a success message at bottom left of the screen, containing the PDF name.
You can then select save to save the T&Cs PDF to the contract.
Once a PDF is saved the View Booking T&Cs text in the summary will show blue (there may be a slight delay whilst the PDF loads).
You can select this to view the PDF document that has been loaded to the contract. This will open in a new window.
Once a PDF has been loaded to a contract, observers will be asked to accept the T&Cs in their app before booking a passenger to a trip that uses the contract.
If a T&Cs document is replaced, by loading a new file in EDIT BOOKING T&Cs, the observer will be asked to accept the new document before proceeding with their booking.
Booking Terms and Conditions - Auth Groups:
You will see a new item in auth Groups called Contract Booking T&Cs, that allows permission to be given to edit Booking T&Cs documents. Newly created orgs will automatically be given permission to edit Booking T&Cs. Where a user has permission to View Contract they will also have permission to View Booking T&Cs. Any user with permission to View Contract will also be given permission to Edit Booking T&Cs.
Waypoint searches in add trip or edit trip were sending unrecognised longitude and latitude to the back-end waypoint API. Back-end validation has been put in place to prevent this and checks are also made to ensure that the longitude and latitudes for newly added waypoints are geographical locations. Front-end investigation of incorrectly entered longtitude and latitudes has been completed and the back-end validation is working to prevent these causing errors.
The Quicksight data sync was causing timeouts, resulting in duplicate alarms for journeys being generated. A short-term fix was implemented but a long-term solution is being put in place over the next couple of sprints. The triggers created for organisations over multiple process have been broken down into smaller parts, with the Quicksight data sync separated.
Ongoing - System Restore from Backup:
The process to back-up and restore Kura systems has been improved to allow for a quicker recovery in the event of a system failure. There are a couple of areas to come
Ongoing - Alarms Prevented From Closing:
There have been a number of alarms that show an error when attempting to action or close. This is caused by a sort key for journey, that occasionally creates duplicates and causes conflicts. The sort key uses event timestamp and has been extended to include nano-seconds, to avoid duplications that prevent alarm action or closure or the over-writing of journey information. The next steps are to transfer historical data to the new database and then to remove data from the old database.
Ongoing - Quicksight Data:
Not all trip data was passed to Quicksight as expected due to timeouts. Work is in progress to prevent timeouts occurring in future and to make any missing data available in Quicksight so that there are no data gaps.