What's new

Dynamic Catering Cut-off

• The new cut-off time per menu defines how many days in advance users can still book for each day of the week. This is helpful to limit booking during the weekend for a Monday, for example. Creating or editing a catering order after the cut-off time is restricted. The details you can find here: Ordering catering in Flex.

Automated Catering Orders

• Automated catering orders are now created when users book the spaces that have this automation set up. The new automated catering order has a corresponding label, a toggle to disable the automated catering order for users to control this service. The details you can find here: Ordering catering in Flex.

Attendees Limitation Settings

• Space capacity now limits the number of attendees that can be invited to the meeting. Users with relevant permissions are able to invite more attendees than the space capacity allows.

What's changed

• We've set the Catering Item quantity limit to 1000 in one order.
• Announcement ribbon on the Home page has now clear indication of the date when it has been published. If the announcement is related to an event, the event date and time should be indicated in-line or linked to the external event's page.
• When moving a booking with visitors to a new building, the new popup helps map their current visitor types to the ones from that target building.

What's fixed

• Improved accessibility issues on the following pages:
  • Spaces Schedule:
    • Added a label for the Sort by dropdown for screen readers.
    • Table headers are now marked as table headers for screen readers.
    • If the screen reader is activated and any information button is then activated, we've fixed the focus order to return to the previous item that was active before opening a popup.
    • When a cell is selected, creating a booking can be enabled using keyboard.
    • Added focus indication to the Jump to Today button when navigating using the keyboard.
  • My Bookings
    • Users can use keyboard to navigate to the Status column.
  • Advanced Booking:
    • We've added the labels for the following fields to be announced by the screen reader: Space Type, Start Date, From, To, Building, Floor, Zone.
    • Enabled typing into the fields Start Date, To, and From when using the screen reader.
  • Change Password under profile dropdown:
    • Labelled all input fields.
    • Relabelled the cross-icon button to close the Change Password popup.
    • The Cancel button now has the focus indication when navigating using the keyboard.
  • My Tasks:
    • Fixed keyboard navigation to open a task for editing.
  • Settings:
    • Delegate Permissions page: improved colour contrast of the sub-headings.
    • System Notifications page: improved colour contrast for the toggle buttons.
    • Workplace Preferences > Search Results: keyboard focus now visible on the list and map view buttons.
• When adding catering to the booking, empty cost codes do not cause an error. Still, the default cost code for the user must be either empty field, empty array, or have a value. It must be present in the JSON object for the user.
• When searching for a space to book a recurring booking, the start time field is validated correctly and doesn't search for spaces in the past.
• On the Simple Booking page, if users change the building after having searched for a space, the start and end time remain as initially set.
• When booking on behalf of someone else and editing cost codes for the booking, the Cost Codes popup shows the cost codes of the booking host.
• On the Advanced Booking page, we've fixed the logic of the Need Events toggle to correctly return all spaces when spaces for events are not needed, not just spaces that don't support events as it was earlier.
• On the Advanced Booking page, the Need Catering filter only worked with the Need Events filter. It is fixed now to work independently.
• Amended the API call for users to be able to save a ticketed event as a draft.
• When cancelling edits for a ticketed event now navigates the user back to the booking associated to the event.
• Fixed rendering of pictures and titles of events on the My Notifications page.
• Visitor records can be opened regardless of their status.
• Under Settings > Workplace Preferences, the user is not able to select working day end time earlier than the start time.

Known issue

• When creating a catering order and switching between menus, the cut-off time in the Order by field isn't changing accordingly.
• On the Advanced Booking page, when you enter all criteria for date and time, and after this select to create recurring bookings, the selected date and time.

What's new

Dynamic Catering Cut-off

• Enhanced the catering cut-off time logic by introducing custom cut-off time options per weekday under Catering Menus.

Automated Catering Orders

• New Catering Template page to set up the default menu for automated catering orders. The spaces that will be using this template are defined in Admin Portal under the booking policies. Read more here: Catering Template.

Attendees Limitation Settings

• Space capacity now limits the number of attendees that can be invited to the meeting. Users with relevant permissions are able to invite more attendees than the space capacity allows. 

What's changed

• Set the Catering Item quantity limit to 1000 per catering order.
• Name and Booking description can be changed for the entire series now.
• Improved accessibility of the Visitor Dashboard page.
• Introduced character limit for descriptive fields on the Visitor Types and Signposts > QuickLinks pages.

What's fixed

• Editing a catering order does not result in error because of an empty cost code field. Still, the default cost code for the user must be either empty field, empty array, or have a value. It must be present in the JSON object for the user.
• The Refresh button on the Space Layout page refreshen the cache for the selected building only.
• When booking on behalf of someone else and editing cost codes for the booking, the Cost Codes popup shows the cost codes of the booking host.
• Visitor records can be opened regardless of their status.
• Upon welcoming a visitor and managing their answers as required by their visitor type, these answers must be saved before you can check in this visitor. 
• Notes can be deleted by the users with applicable rights and not only users who created the note.
• Made the whole View Event Page clickable instead of just a clickable arrow on the the Edit Event page.
• When duplicating an announcement, the duplicate has now all necessary fields filled in the payload and is fully valid record.

What's new

Automated Catering Orders

• New Automated Catering Order (Optional) section in the Space booking policy settings to add a catering template. The catering template must be created in OneLens first. View the details here: Space booking policy.

Attendees Limitation Settings

• New role-level permission API.Bookings.UnlimitedCapacity allows users add more attendees than the space capacity is set for.

Other

• The Space page has a new option to define this space as arrival location for visitors.

What's fixed

• When creating a signpost and adding an image, we've added more guidance around what image sizes are recommended for best results.

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.