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

Catering

• If the catering order is cancelled before the catering menu cut-off time, its status is changed the following way:
  • If the preparation time has started for any of the catering items (Preparation Time under the corresponding Order Policy), the status then is Cancellation Pending for the catering team to decide if the user should be charged.
  • If the preparation time hasn't started, the status is Cancellation No Charge.
• When the booking that has catering orders is extended (end time has been increased), status of the catering order doesn't change.

Bookings

• Updated POST /v2/{nodeid}/bookingparties for Booking_Parties_Formatted field to be now comma separated instead of being separated by semicolons.
• DELETE /v2/{nodeid}/bookingparties/{recordid} and PATCH /v2/{nodeid}/bookingparties/delete now update the Booking_Parties_Formatted field to remove the deleted party in the booking record.

• We've optimised the 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

• We have corrected the floor availability calculations for the endpoints:
  • /v1/{nodeid}/Floors/{floorid}/availability
  • /v1/{nodeid}/Floors/{floorid}/availability-and-environmental

Visits

• PATCH /v2/{nodeid}/bookingparties/delete whether used in Hub or via API removes the booking party and only cancels the visit. Previously the whole visit record would be removed from the system.
• When adding an external visitor to the booking, a corresponding visitor record is created with host details properly populated. Previously, host details weren't populated.
• Similarly, when the host is changed for a booking with an external visitor, the visit record is properly updated with the new host details.
• When creating a visit linked to a booking via the POST /v2/{nodeid}/bookingparties endpoint, the OwnedBy field of the visit record is now correctly set for the Booking Owner. Previously, current user was set as the owner.
• When a booking with an external visitor is moved to a different floor, visitor record is moved along accordingly now. Earlier, the visitor record used to detach from the original booking.
• If a booking with a cancelled visitor is moved to a different floor, the cancelled visitor has been previously recreated in the booking. We've resolved this issue now.

Booking on behalf of a visitor

• When a booking is created on behalf of a visitor and then the booking time is updated, corresponding visitor record is now also updated with the same time for the visit.
• When booking is created on behalf of a visitor, this visitor is a booking owner and doesn't count as an attendee. This now resolves the exceeded space capacity error.

Catering

• PUT /v2/{nodeid}/catering-order/{orderId} call now validates IgnoreCutOff permission when attempting to update a catering order after the Catering Menu cut-off time.
• When an approved catering order is updated with a new name or description, its status doesn't change any more. Previously, it would move to Pending Approval.
• When a catering order is in Pending Approval status and is moved to a space where the menu is not available, the order is set to Cancellation Pending.
• If the user with the IgnoreCutOff permission moves a booking with the approved catering order to a different space where the same menu is available, the catering order status remains as approved. Previously, it would be set to Cancellation Pending.
• When updating attendees number for a booking with automated catering order, quantities for such order are now correctly updated too.

• When updating a booking with fully used capacity, resources are not added to the attendee count anymore. Resources can be added to the booking as needed.
• When updating a booking with added resources, the resource is re-added to the new booking if available.
• When the resources that have been added to the booking are released, these resources return to available state and can be used for another booking.
• When creating a booking for a visitor, a duplicate Booking Party isn't created any more, and the booking is successfully created without (wrongly) exceeding capacity limits.
• When updating a booking for a visitor, the following fields are updating correctly to reflect changes made to the booking: Booking Is Visitor, Booking Party count, Booking Parties Formatted.

• 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 gets 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.

Known issue

• When moving a booking with external visitors to a different building using the POST /v2/{nodeid}/bookingparties, the Visitor Type field is not updated with the new Visitor Type assigned for the visitor. Check in experience for such visitors must be handled manually for now.
• Adding or removing attendees to the booking with catering does change quantities for automated catering orders. But if the Booking Attendance field is the bigger value entered manually, it should override the Booking Parties count (number of attendees) which is not happening at the moment until the next product release.