- The Android app version has been updated to: Native: 2.0.1, JS: 2.1.2
- iOS remains as: Native: 2.0.0, JS: 2.1.2
The latest version has been released to the Android store 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.
Support for Galaxy S6 Edge:
A number of users reported that the app crashed when using a Samsung Galaxy S6 Edge device. This has now been resolved and Galaxy S6 Edge devices are supported, with the app functioning as expected.
Apple released iOS 14 without notice on 17th September. The app has been tested and is compatible with iOS 14.
In App Booking Terms and Conditions:
Work for this item is in progress and we expect that this will be included in the next release.
Work was started to show Booking Terms and Conditions (T&Cs) when an observer adds a passenger to a trip in their app. The Terms and Conditions will show where an observer selects 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.
The below items are in progress and we expect that these will be included in the next release.
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:
A new auth group permission item will be added for Contract Booking T&Cs. During the next two weeks permissions will be applied to the Contract Booking T&Cs so that, when this feature is released, newly created orgs will automatically be given access to Edit Contract Booking T&Cs. Where a user has permission to View Contract they will also have permission to View Contract Booking T&Cs. Any user with permission to View Contract will be given permission to Edit Contract 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.
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 in progress. The triggers created for organisations over multiple process have been broken down into smaller parts, with the Quicksight data sync separated.
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.
Items released during the last 2 weeks:
Profile Metric Reporting:
With increased visibility of profile data within Quicksight, we can see that Kura currently has just under 30,000 profiles setup. So far in 2020, the Kura operations teams have handled 48,500 alarms generated for managed organisations, and there have been close to 200,000 passenger boarding events.
Person Search - Tokens:
So that you can quickly locate the owner of a lost tag, or identify a previous user of a tag to remove and re-allocate, the Persons page search now includes token ID (NFC tag or RFID serial number).
A complete or partial token ID can be entered to show results.
This search is case sensitive (as serial numbers are case sensitive).
Please note that, as only passengers have token IDs, search results will only be shown where the Passengers or Total card is selected.