What's New?

As we continue to release updates, we continue to add new features to our products. This section provides details about what has been added to the products:

• Restructured menu for future updates
• The booking list DataGrid allows users to search for, filter and sort bookings more easily including taking actions directly from the data grid, to minimise clicks.
• The visitor list DataGrid allows users to search for, filter and sort visitors more easily including taking actions directly from the data grid, to minimise clicks.
• Ability to apply catering menus to specific spaces.
• Ability to view cost codes that have been imported into the system.
• V2/Booking API – Advanced Booking APIs that also take into consideration the new Booking Policies that can be applied to spaces.
• V2/Spaces search API – The search API’s ability has been enhanced, to recognise and handle the advanced booking policies, so that these are factored directly into the search and the results it provides. 
• V2/Task Api – As part of making improvements to upcoming catering capabilities a new tasks API has been created to handle catering orders and the tasks associated with it. 
• Cost codes APIs have been updated to handle the platforms’ ability to use one or more cost codes against a booking or catering order and apportion the amounts to individual cost codes.
• Ability to import cost codes via an SFTP shared flat file update, and recurring deltas to keep them up to date. 

What's Fixed?

Several fixes have been implemented to resolve issues found in the product.

• Resolved an issue where users were logged out automatically.

Known Issues

This section describes issues that users of OneLens 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. 

Core/API Updates

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.

• V2/Booking API – Advanced Booking APIs that also take into consideration the new Booking Policies that can be applied to spaces.
• V2/Spaces search API – The search API’s ability has been enhanced, to recognise and handle the advanced booking policies, so that these are factored directly into the search and the results it provides.
• V2/Task Api – As part of making improvements to upcoming catering capabilities a new tasks API has been created to handle catering orders and the tasks associated with it.
• Cost codes APIs have been updated to handle the platforms’ ability to use one or more cost codes against a booking or catering order and apportion the amounts to individual cost codes.
• Ability to import cost codes via an SFTP shared flat file update, and recurring deltas to
  keep them up to date.

What's Changed?

The following core platform and API changes have been made: 

BookingParties changes have been updated to allow for separate hosts vs owners of

• BookingParties changes have been updated to allow for separate hosts vs owners of meetings in preparations for improvements in future releases.
• V2/Task Api – As part of making improvements to upcoming catering capabilities a new tasks API has been created to handle catering orders and the tasks associated with it.
• Additional fields have been added to the Notification APIs, UserPrefs API, details of which can be found in the SWAGGER documentation bundled with the release.
• We have insured that the Bookings API is now consistent with handling data types for specific fields.

What's Fixed?

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

• Resolving an issue where it was possible to change visitor the start and end times of visitors in the past.
• Fixed an issue where pushing a notification would create a 500 error in the system.
• Resolved an issue where visitors could not be cancelled because of missing information in the record.
• Fixed an issue where requesting tasks via the API would sometimes report at 0, rather than have any useful information. 
• Fixed an issue where Colleague finding was not correctly returning the expected results.
• Fixed the Visits-download API to correctly download the visitor data.