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

• Catering Item preparation time is now a key decision factor for how the catering order status changes depending on when the catering order is being modified. This is made mainly to ensure that the the user is charged or the catering team decides if they are charged if the preparation has been started before any changes are made to the catering order:
  • 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.
• We're allowing users with the permission Catering.OperationalServices to edit catering orders after the order has been completed. This is used in case the catering order needs to be corrected for the record. The current status of the catering order will not change if it's edited past order end time. Previously only users with the IgnoreCateringCutoff permission could edit completed orders.

• We've added an option on the Visitor List page to display maximum records from 200 to 1000.

• 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

• When searching for a visitor by their first and last name, the record failed to return previously because the visitor's the name is split into individual firstname and lastname fields, and if the user was to type a full name, it wouldn't match any of the values in the response. We've fixed it by creating a full name field.
• On the Booking List page, when searching for a record by user's name, all relevant records are returned. Previously the system would search only for email assuming that the email and name are the same. Now the system will find relevant records if the person's name and email differ.
• On the Visitor List page, the search functionality works correctly across paginated results. Previously the table would default to the first page.
• On the Booking Dashboard page, when updating a booking, the cost code used is retained and included in the PUT/v2/{nodeid}/bookings/{bookingid} call.
• We're removing the unavailable menu item from the payload when the catering template is updated. Previously unavailable items caused an error.
• Searching for a visitor by their full name has been fixed. Earlier, the search would work for either first name or last name. Now the validation works for the full name too.

• When setting a task in progress, the system checks first if the comment has been added to avoid unnecessary call for a comment update. If the comment is there, IBSS makes these two call to the API one after another now. It has been processed simultaneously before and causing an error.

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

Known issue

• On the Space Layout page, the updates to existing layouts wipe out previous settings and save just the most recent ones. Contact IBSS Customer Support to help you introduce adjustments to furniture layouts or to link spaces in one bookable configuration.