Release Notes - OneLens & Admin Portal - R2023.01.02 - 2023-09-22

Written By Noel Thethy (Super Administrator)

Updated at October 16th, 2023

What’s Fixed?

Several fixes have been implemented to resolve issues found in the products. These include:

  • Fixed an issue in Admin Portal where it was not possible to create new native user.
  • Resolved several issues around the rendering of the permissions page in the  Admin Portal
  • Fixes an issue in OneLens does not display in the booking export function.
  • Resolves an issue when using the checkout action in OneLens the
    Booking_Owner_Email needs to be included to allow check out of behalf of.
  • There were several minor styling changes made to the Booking Policies page in the Admin Portal.
  • Resolved an issue where the incorrect message was shown when rejecting a booking.
  • Fixed an issue in OneLens where approved or auto approved Bookings do not have the Cancel Button in the Action Column.
  • Resolved an issue where the system would duplicate user entries when modifying attendee/visitor information.
  • Resolved an issue where it was not possible to create a new role via the user interface successfully.
  • Fixed a OneLens issue where Date & Time Period Type displays as Undefined when a user attempts to Filter search criteria.
  • Resolved an issue where the save button was inactive when adding a visitor with nontypical email address.

Known Issues

This section describes issues that users of OneLens/Admin Portal may encounter, as well as workarounds for these issues. It goes without saying that we are already in the process of fixing these issues.

There are several pages that contain visual alignment issues, as we continue to progress towards moving to a new standard of component library. While these should not impact overall usability, we are aware that this means the user interface may not be ideal.

IBSS Platform and API

As part of the continued development of the platform, and to support the new features mentioned above, we have also made changes to the IBSS platform.

What's New?

As part of our endeavours to add new features in to releases, the following back-end API additions have been made available.

  • When a user with book on behalf of rights and chooses to auto check in, this should override policy setting [v1 booking compatibility].
  • Added the ability to see debug timings on IBSS API v1/Bookings/search call and review for optimisation.
  • Add the ability to see debug timings on IBSS API V2 calls (POST bookings).
  • Add the ability to see debug timings on IBSS API V2 calls (POST search-recurring).
  • Add the ability to see debug timings on IBSS API V2 calls (search).
  • Get the space name (or label) from the spaces table for the GET /v2/{nodeid}/bookings and /v2/{nodeid}/bookings/download.
  • Review V2 Spaces Search for performance optimisations .

What’s Changed?

The following core platform and API changes have been made:

  • Change GetNewDefaultUserPrefJsonString to get the defaults from a blob storage file.

What’s Fixed? 

We continue to improve and make bug fixes where necessary, including:

  • Resolved an issue where the API was unable to use Booking Parties Calls in V2 despite having full set of permissions and data security.
  • Resolved an issue where the Booking_Not_Found 'Message' field did not return the BookingId
  • Fixed an issue where SpaceCateringMenu call was not retuning MenuId in Message field.
  • Fixed the API issue where Booking_Participant_Checkin and   Booking_Participant_Status was incorrect when a booking is checked in and amended then completed.
  • Resolved the IgnoreTimeHorizon rights not working as expected even as it is being applied. 
  • Fixed an issue where manually rejecting a booking, doesn't transition the booking party to cancelled.
  • Resolved an issue where recurring booking availability is not returned if single space types are assigned to multiple policies.
  • Resolved an issue where the API would not allow a user to update a booking after being checked-in.