What's new

Dynamic Catering Cut-off

• New fields in the CateringMenu GET/POST/PUT/PATCH methods to support new cut-off settings under Catering Menu.
• Cut-off time validation in the CateringOrder POST method.

Automated Catering Orders

• New endpoints and permissions to support Catering Template functionality as well as changes to the booking policy API to attach Catering Template:
  • GET /v2/{nodeid}/catering-templates
  • POST /v2/{nodeid}/catering-templates
  • GET /v2/{nodeid}/catering-templates/{id} 
  • DELETE /v2/{nodeid}/catering-templates/{id} 
  • PUT /v2/{nodeid}/catering-templates/{id}
  • DATAMODEL.CateringTemplate.Create
  • DATAMODEL.CateringTemplate.Read
  • DATAMODEL.CateringTemplate.Update
  • DATAMODEL.CateringTemplate.Delete
• Made the following changes to support creating automated catering orders upon booking creation:
  • Added TemplateId to GET /v2/{nodeid}/bookings/{bookingid} response.
  • Added IsAutomated to POST/PUT/PATCH v2/{nodeid}/catering-order.
  • Modified POST v2/{nodeid}/bookingparties?bookingid={bookingid} as well as IMPORT v2/{nodeid}/bookingparties/import/{bookingid} to increase or reduce automated catering order count if attendees number is changed.

Attendees Limitation Settings

• To support new functionality of limiting attendee invitations depending on room capacity:
  • Added a permission API.Bookings.UnlimitedCapacity that uses building permissions (AppliesTo).
  • Made changes in Bookings, BookingParties endpoints.
  • Created a new endpoint under BookingParties POST /v2/{nodeid}/bookingparties/bookings-series/{seriesid} to support booking series.
  • v2/{nodeid}/bookingparties now use limitations as set by the space capacity value.

What's changed

• We've optimised booking export process.
• Visitors permissions have been merged with the Visits permissions and therefore removed from the Data Security table under Admin Portal > Setup > Security > Role & Data Security.
• Booking call payload has been amended to handle the Booking Parties call separately.
• Users who are set up as guests in AAD can login to IBSS hub or API.

What's fixed

• Fixed creating a task for equipment.
• Visits can be extended after the visit start time.
• Fixed importing attendees as booking parties using the POST /v2/{nodeid}/bookingparties/import/{bookingid} endpoint to support the Ticketed Events functionality.
• Fixed a set of error responses to improve user experience in IBSS HUB apps:
  • Invalid cost code error message has been added.
  • When the booking start time is later than end time, the error is now Booking_Invalid_Times
    instead of Booking_Invalid_Duration_Too_Short.
  • Error for the incorrectly set up linked spaces gives more details now explaining the issue.
  • Error when cancelling a linked space booking is now in RFC 9457 format as all other errors in IBSS.
• Fixed a formatting issue to accept empty cost code field for catering orders.
• When updating a booking policy using PATCH /v2/{nodeid}/bookingpolicies/{bookingpolicyid}/Apply, the new Booking Policy ID get stored in IBSS data bases.
• Visitor Types now accept the name with an apostrophe.
• Booking start and end time for booking series is now correctly using the UTC format.
• Creating a recurring booking for a space that doesn't require setup and reset slots around it now returns the ParentBookingId as empty string and not as null.
• As updating a booking within approval window is not permitted, we've fixed this validation to include the setup and reset slots around the booking before an error is shown.