Skip to main content

 These release notes provide information on the new features, enhancements, resolved escalations, and bug fixes completed in each release of the Room Booking card.

Important

For each release, the updates are pushed to the card template in the Library. Cards created prior to the latest release will not receive the latest updates. To get the latest feature or bug fix for this card, the card must be recreated with the latest template.


 

v 1.30

Release Date: 6 July 2023

FEATURE IMPROVEMENTS

This improvement is only applicable to the Appspace provider and is disabled by default.

  • Allow for modifications to the size of the QR Code.
    • The verification confirms that users, when selecting the Appspace provider, have the ability to check or uncheck the “Enable QR Code for touchless reservations” option.
      • When the option is checked, the QR Code drop-down will be displayed, providing the user with the ability to select the desired size. The default size is set to “Small”.
      • When unchecked, the QR Code dropdown will be hidden.

This booking option is enabled by default.

  • The booking options section now includes the newly added option to “Allow users to book meetings”.
    • This new option allows the user to enable or disable the booking of meetings on the card.

FIXED BUGS

  • CT-3764 – The QR Code Size schema should only be visible to the Appspace Provider.

Patch Updates

v 1.30.1

Release Date: 1 Aug 2023

FIXED BUGS

  • CT-3769 – Screen dims when tapping the “Try to Reconnect” button, if the Schedule Room card has been configured with the Appspace provider.

RESOLVED ESCALATIONS

  • AE-9410 – The Room Schedule card goes offline after the Logitech Tap Scheduler reboots.

 

 


 

 

v 1.29

Release Date: 14 June 2023

FEATURE IMPROVEMENTS

  • Allow customization on the Room NameRoom Label, and Room Notes.
    • When using the “Automatic Room Assignment” mode, the user is now allowed to customize the Room Name, Room Label, and Room Notes.

FIXED BUGS

  • CT-3754 – A new separate meeting is created in the “Upcoming meetings” list, even when failing to extend the initial meeting of a non-editable resource.
  • CT-3753 – The Room status still switches to “Occupied”, even when failing to check in on a non-editable resource.

RESOLVED ESCALATIONS

  • AE-9334 – Unable to Check-in when using Appspace resources

 

 


 

 

v 1.28

Release Date: 15 Nov 2022

FEATURE IMPROVEMENTS

Support Additional Checkpoint Conditions

  • Resource checkpoints will only be shown if they match the following conditions:
    • Applies to > “All”
    • Valid From
    • Valid Until
    • Active Period
  • Inherited checkpoints will only be shown if they match the following conditions:
    • Valid From
    • Valid Until
    • Applies to > “All”
    • Target Resources > “Rooms” / “Spaces”
    • Active Period
    • Sub-Types > applicable only if the resource subtype matches

FIXED BUGS

  • CT-3294 – The capacity rules are not applicable when resources are set to multiple rules.
  • CT-3524 – Checkpoint appears on the Room card when the validity date has expired.
  • CT-3529 – When setting the checkpoint Valid From (Immediately) in the Edit Rule tab, the checkpoint does not appear when attempting to do an advanced booking.
  • CT-3532 – Checkpoint waivers are showing up for room check-ins when they are configured to affect only buildings.

RESOLVED ESCALATIONS

  • AE-8513 – Checkpoint waivers are showing up for room check-ins when they are configured to affect.

Patch Updates

v 1.28.1

Release Date: 14 Feb 2023

RESOLVED ESCALATIONS

  • AE-8838 – The card.room.facilities feature is not updated on the devices when it is removed or modified.

 

 


 

 

v 1.27

Release Date: 11 Aug 2022

FEATURE IMPROVEMENTS

  • When you add a Max capacity constraint rule for any resource, the correct maximum capacity is now reflected on the card.

     

  • Added ability to modify the font size up to 300% for Room Name display on larger screens, when configuring manual room assignment in the card.

FIXED BUGS

  • CT-3267 –When an imported Appspace provider resource has check-in constraints, instant booking fails.

 

 


 

 

v 1.26

Release Date: 19 July 2022

FEATURE IMPROVEMENTS

  • Additional Room Facilities icons have been added, allowing for new facilities to be displayed on the Room Schedule card.
    • The Room Facilities icons would need to be configured with the “card.room.facilities” device property together with the following values below:
      • Webex: “webex”
      • MTR Dual Display: “mtrDualDisplay”
      • USBC Dock: “usbcDock”
      • Flexible Furniture: “flexibleFurniture”
      • Hearing Assisted: “hearingAssisted”

FIXED BUGS

  • CT-3132 – The logo is cropped when displayed on a 16:9 resolution screen in portrait, or when displayed on a mobile device screen in both portrait and landscape orientations.

 

 


 

 

v 1.25

Release Date: 26 May 2022

FEATURE IMPROVEMENTS

 

 

  • The font size of the room name displayed on the Room Schedule card can be modified by the user.
  • Users can add custom text for display at the bottom of the card.

Patch Updates

v 1.25.1

Release Date: 21 June 2022

FIXED BUGS

    • CT-3146 – When attempting to book a room using the Book Now button for a future meeting slot, the meeting prior to the slot is ended earlier than scheduled, and the user is unable to book the room before the next 30-minute block. The card displays the, “We’re having trouble booking your meeting. Please try again.” error message.
    • CT-3166 – During check-in, devices configured with a custom provider are stuck at the “We’re checking you in…” window.
    • CT-3191 – During check-in, devices and browsers configured with custom providers take a long time before the “We’re having trouble checking you in. Please try again.” error message is displayed.

 

 


 

v 1.24

Release Date: 10 Feb 2022

Resolved Bugs
  • CT-2841 – Unable to load Room Schedule card on the Cisco Webex Board, Crestron TSW-1060, and Mersive Pod Gen3 devices, due to exceeding the local storage limits.

Resolved Escalations
  • AE-7645 – The organizer’s name does not display when configured with Microsoft 365.

 

 


 

 

v 1.23

Release Date: 10 Nov 2021

Updates for Occupancy Sensor

Important

This feature requires custom integrations that leverage Appspace APIs, while some sensors may also require device tasks in order to function correctly. To utilize this feature, please contact Appspace Support.

 

  • A pop-up notification is displayed for the following meeting states when the Room Schedule card is used with an Occupancy Sensor:
    • Create
    • Extend
    • Check-in
    • End
  • The notifications will appear for 5 seconds and are then removed.
  • A new Occupancy Sensor Settings tab is added to the card editor.

 

 


 

 

v 1.22

Release Date: 8 Oct 2021

Room Schedule Enhancements
  • The Room Booking and Desk Booking cards are now listed under the Workplace template type, as part of our product realignment exercise.
Support for Occupancy Sensors

 

 

  • Room Schedule cards will now support third-party occupancy sensors, that can be used to manage the room status through custom integrations that leverage on Appspace APIs, with some sensors requiring device tasks in order to function correctly.
  • Users would also be required to check the Enable occupancy sensor checkbox on the card for the feature to work.
  • Users may also determine the following duration of the room status (defaulted at 3 mins) based on the room occupancy of the room occupancy:
    • Automatically check-in based on occupancy
    • Automatically create a new meeting based on occupancy
    • Automatically end meetings based on occupancy
    • Automatically extend meetings based on occupancy

 

 


 

 

v 1.21

Release Date: 22 Sept 2021

Support for Automatic Room Assignment for Appspace Resources

Once a Room Schedule card has been configured with the Automatic Room Assignment option, Admins are able to assign an Appspace resource from the Device Settings tab, via the Reservation Resource drop-down menu.

 

 

This feature is currently only supported on resources configured with the Appspace calendar provider, and will take precedence over the card.room.roomid device property value that is configured to the device.

Be the first to reply!