Android: Native: 2.3.2, JS: 2.3.2
iOS: Native: 2.3.2, JS: 2.3.2
There have been no updates to the app in the past two weeks.
Archive Profile - Software Customers:
Software customers are now able to archive a profile manually where someone has left their organisation. When a profile is archived:
Passengers will be removed from any scheduled trips,
Any user account will be unlinked,
Links between observers and observees will be broken,
Any auth group will be removed.
To archive a profile select Profiles from the navigation menu. Select the cog on the required profile card to open the profile details modal. The select the Edit Profile button:
Select Edit Profile and an Archive button will be displayed:
Once this has been selected a confirmation screen will be opened where you are required to enter the exact profile name to proceed. Entity name entries auto-capitalise and the submit button will only display when there is an exact match, including required spacing.
Once you have entered an exact entity name match you can submit the request and will see a confirmation message appear in the modal:
You will see that any linked user account has been removed from the profile and any observer or observee links have been broken.
The user will no longer be able to login to the app or Kura portal.
If the archived profile is for a passenger, and observers are not archived, as they also observe other profiles within the organisation, the observers will no longer see the passenger within their app.
If a passenger profile is archived the passenger is removed from any schedule trips and these removal events will be shown in the Legacy Bookings table:
Please note that, where the user is an emergency contact, when Archive is selected a message will be displayed to notify the user that emergency status must be removed before a profile can be archived:
Welcome Screen - No Link:
Where a user has created a Kura account without receiving or following the steps in an invitation, so that no attempt to link to a profile is performed, a message now displays to let the user know that they need to receive and follow the steps in their invitation.
Legacy Bookings Summary:
If a user navigated to a page in the table and then selected a different start and end date from the filters, the date filter would no longer work until the page was refreshed. This has been resolved and the date filters apply where a user has navigated to further pages in the table.
Also, if a user navigated to a page in the table and then selected a date range that contained no booking or removal events, this would cause the page to crash. This has been resolved and the table returns a 'No records to display' message, so that a user knows that no data is available for the date range selected.
If a user navigated to a page in the table and then selected a date range that contained no booking events, this would cause the page to crash. This has been resolved and the table returns a 'No records to display' message, so that a user knows that no data is available for the date range selected.
Zonal Pricing Grid:
The zonal pricing grid vertical scroll bar wasn't appearing for Windows users. This has been resolved so that, where more than 10 rows have been added to the grid, the vertical scroll appears to navigate the grid.
Payment Installments (ongoing):
Initial investigation is in progress to integrate Stripe subscriptions; to allow organisations that opt to use payments to split customer payments into installments according to the value of their booking.