What's new

• Added the following permissions to support new functionality:
  • API.Bookings.OverrideSetupTeardown
  • API.Bookings.BookOutsideSlots
  • API.Bookings.ShowPersonalInformation
  • API.Users.CheckPin
  • ADMINPORTAL.PortfolioSetup.TagDefinitions
  • ADMINPORTAL.Users.ShowUserPreferences
  • FLEX.UserPreferences.CostCodes
  • ONELENS360.OperationalServices.OrphanedUsers
• Enabled the newly introduced default setup and reset times to be used by booking policies.
• Introduced a setting to define the period of time after which the historical visitor records are removed from the archive.
• Implemented compliance mechanisms with GDPR and other privacy regulations.
• Introduced new mechanism to store the audit log.
• Enabled use of Tags functionality.
• Enabled use of System Filters functionality for all apps in Hub.
• Enabled Notes functionality for the Bookings and Visits record types, where, for now, HUB uses the one for Bookings only.
• Created new endpoints:
  • GET /v2/bookings-summary/daily
  • GET /v2/{nodeid}/spaces/{spaceid}/catering-menu
  • GET /v2/{nodeid}/bookings/my-primaries-bookings
  • PATCH /v2/{nodeid}/bookings/{bookingid}/deny
  • PATCH /v2/{nodeid}/bookings/{bookingid}/approve
• Added a new search validation test around recurring bookings.

What's changed

• Reviewed the heartbeat protocol.
• Migrated IBSS API to .NET 8.
• Changed the mechanism that IBSS uses for sending emails. This change has no impact on users.
• Enabled string trimming for the Identity Providers and Identity Provider ID calls to make sure that clientId, tenantDomain, tenantId, clientSecret, name, additionalAudiences, and nameClaimType are all trimmed.
• Improved performance by removing the TelemetryClient.Flush() method.
• Removed the following permissions:
  • API.Bookings.IgnoreAllPolicyRestrictions
  • ONELENS360.OperationalServices.DeletedUsers
• Removed recursion for catering calls except for Catering Orders.
• POST V2 spaces/search returns now full date and time with the trailing Z.
• Optimised error and cancellation handling for the following calls:
  • POST /v2/{nodeid}/spaces/search
  • GET /v2/{nodeid}/bookings/download
  • GET /v2/{nodeid}/catering-menu/download
  • GET /v2/{nodeid}/catering-menuitem/download
  • GET /v2/{nodeid}/catering-order/download
  • GET /v2/{nodeid}/catering-order-policy/download
  • GET /v2/{nodeid}/catering-restriction/download
  • GET /v2/{nodeid}/catering-supplier/download
  • GET /v2/{nodeid}/spaces/download
• Updated the following endpoints to include the Space_Name and Space_Id fields:
  • POST /v2/{nodeid/visits
  • PUT /v2/{nodeid/visits/{visitid}
  • PATCH /v2/{nodeid/visits/{visitid}
• Merged into one the three API calls for setup, main booking, and reset slots.
• Handle recurring bookings as part of the Series bookings approach.
• Made updates to handle Orphaned Bookings.
• Connectors Configuration data model is now part of the Event Type definition in SQL.
• Improved Request Model.
• Removed booking validation tests:
  • VT007 Does the specified space allow bookings by admins only
  • VT012 Is the booking start date on a day that the space is not available
  • VT018 Is the specified party more than the capacity
  • VT025 Does the booking overlap with any other booking made by someone else for the same space
• Changed booking validation tests:
  • VT011 Is the booking start date on date that the space is not available
  • VT013 Is the booking start date on day after the booking horizon 
  • VT014 Is the booking start/end time outside the hours specified for this space in the booking policy 
  • VT023 Does the user have the right to make a linked booking 
  • VT024 Does the booking overlap with any other booking made by Owner of the booking 
• Extended /v2/{nodeid}/catering-order to include Booking start and end if associated to a booking.
• Changed which characters are supported in creating a Visit ID. Excluded are: 0 1 2 3 5 A E I O U L N S Z, supported characters are: 4 6 7 8 9 B C D F G H J K M P Q R T V W X Y.
• Deprecated V2 catering-order/order-items endpoints.

What's fixed

• Removed defaults for all app settings that are set by the user.
• Added all available permissions to the Admin Portal UI.
• Implemented the duplicate user check to handle the error when creating a new user.
• Environmental Zone Summary is now properly calculated.
• Fixed the file uploading issue.
• Reduced unnecessary calls in the system when making requests to fetch bookings.
• Fixed error codes and error messages.
• Booking Policies are validated against Node ID and Space ID.
• GET /v2/{nodeid}/bookings/download now properly handles the xxx_local time fields.
• Fixed the issue when the booking owner name has been changed to their email when editing the booking that was made for someone else.
• Fixed the error message for booking outside of the building office hours.
• Fixed the error message for invalid booking times to include dynamic details.
• It is not possible to move a task to assigned state if the resolver is not indicated.
• Fixed also the task to move to the Awaiting Re-Allocation state if it is unassigned.
• Visits are now returned for Node ID 1.
• If the start time is less than 5 minutes in the past, the API will add 5 minutes to the start time, so it isn't rejected. This primarily impacts booking on Unity and single booking in Flex.
• If a building is set to require visitor approval, visitors aren't approved automatically anymore.
• If a booking is made on behalf of someone else and the Booking_AutoCheckIn field is in the booking policy, the booking is auto-checked in and does not auto-cancel if not manually checked in.
• Updating a booking that was created on behalf of someone else is now setting the owner fields correctly.
• Ensured hat Booking_Share_Loc is correctly filled out in the Booking Parties table based on the user preferences.
• Fixed the Space_Work_Type filter and POST /v2/{nodeid}/spaces/search supports it now.
• GET/v2/{nodeid}/catering now correctly uses Floor Node ID instead of Building Node ID.
• PATCH v2/bookings correcly checks for linked spaces.
• GET /v1/Service/CachedData works only when the user is logged in.
• Fixed booking on behalf on someone else that was caused by incorrect cost code allocation.
• Fixed booking name population for the new visitor record.
• Permissions to create recurring bookings works properly now.
• Fixed displaying user's bookings if they have no permissions to book on behalf of someone else.
• The booking is auto checked in with the booking start time if enabled.
• GET /v2/{nodeid}/bookings returns all correct booking parties and booking resources.
• PartyCount removed from the example payload in V2 Bookings POST/PUT/PATCH endpoints.
• If using PATCH /v2/{nodeid}/spaces/{spaceid}/checkin to check in to the space or PATCH /v2/{nodeid}/spaces/{spaceid}/checkout to check out, the booking needs to be created in UTC time zone.
• If creating a booking using POST /v2/{nodeid}/bookings call, and then use PUT /v2/{nodeid}/bookings to change the space to the one on a different floor, original Booking Parties are now cancelled and not updated to have the new Space IDs.
• Space availability validation is fixed and respects setup and reset times for existing bookings.
• Disabled creating a visit with the same start and end time using the POST /V2/{nodeid}/Visits call.
• Booking cannot be created if it requires setup and reset activities and the setup time starts in the past.
• Spaces cannot be search for the time in the past.
• Start time cannot be edited for the booking that requires setup and reset time once the setup time has elapsed. Booking details such as name, description can still be updated.
• Space_Arrival_Loc is enabled when adding a visitor.

Known issues

• IBSS supports 300 nodes per environment now, buildings and floors included. Read more here: Number of nodes within one environment.
• Column sort options have been disabled in the user interface. The ability to sort is expected to be added directly to the API in an upcoming release.
• If someone makes a linked space booking, it is possible that this booking is not counted towards the bookings a user is allowed to make. This means that some people may be able to book a desk, a single room, and a linked room all at the same time.
• When two users are defined using two different AAD connections, but both users have the same email address, than the system may not always be able to determine which of the users has been selected. The recommendation is to not have two users with the same email address.
• Building announcements are sent on creation instead of the selected Available_From time.
• Maximum recurrence that is set by the booking policy is not enforced for this release and will default to 52.
• You cannot edit a booking of a single space to a booking of linked spaces or a booking with a different layout because such bookings require a setup and reset time slots before and after the meeting and they are not automatically added for now. Delete your current booking and create a new one with layout or linked space instead.
• Once the visit has been checked in, user can no longer update the Visit Record.