Changes
key | Touchpoint | Release Notes |
GO | Recurring group reservations for workplaces Earlier, users could create group reservations or recurring reservations separately, but it was not possible to create recurring reservations for a group in a single flow. Users had to manually create recurring reservations individually for each person, which required additional effort and increased the chance of errors. With this enhancement, users can now create recurring reservations for group reservations in a single go. After selecting multiple users under Group Reservation, a new “Make recurring” option is available in the reservation details screen to define the recurrence pattern. The system will create individual recurring reservations for each selected user and workplace (up to 20 workplaces in a single flow), thus creating all the recurring reservations in a single go. The notification system has been updated to reflect this change, and the booking success message now clearly indicates which recurring reservation has been submitted to which recipient. Both the creator and recipients can manage these reservations from their respective My Reservations tabs. Benefits:
| |
GO | Improved display of additional information in the service request screen Earlier, long Additional Information text in the Create Service Request screen was displayed in a single line with an ellipsis inside a text box, making it appear like a non-editable input field and limiting visibility of the full content. This has now been improved. The Additional Information is displayed as static text instead of a text box, and long content is shown clearly across multiple lines. This ensures better readability and avoids confusion for users. | |
GO | Improved availability search performance Earlier, when searching for available rooms, workplaces, or other reservable resources—especially in large buildings—users could experience slower response times due to system processing of availability and access checks. With this improvement, the availability search has been optimized to load results significantly faster, even for large buildings with many reservable spaces and access rules in place. Users will now experience quicker loading times when viewing floor availability or searching for spaces. Benefits: Faster search results for rooms and workplaces | |
Studio | Updated space terminology in studio dashboards To improve clarity and consistency in terminology, several space-related labels have been updated in Studio Dashboards and related configuration screens ( Category location mapping) Label Updates: Updated Space Class Mapping Values: These changes are terminology updates only and do not impact existing functionality. |
Bugs
key | Touchpoint | Release Notes |
GO | Prevention of duplicate visitor records during import Earlier, when the same visitor import file was uploaded multiple times, duplicate visitor records were created in the system. This issue has now been fixed. The system will prevent duplicate records from being created when the same visitors already exist. Additionally, a clear error message is now displayed to inform users that the record already exists. | |
GO | “Find a Colleague” weekly view and crowdedness indicator An issue was identified in the Find a Colleague feature in GO, where selecting the Week view showed zero results and a 0% crowdedness indicator, even when reservations existed. Similarly, when using the “All Colleagues” filter, no colleagues were displayed despite valid bookings. However, results appeared correctly when using Today, Tomorrow, or specific future date filters, and when filtering by Favorite Colleagues. This issue has now been fixed. The Week view and “All Colleagues” filter now correctly display colleagues with reservations, and the crowdedness indicator reflects accurate occupancy data. | |
GO | Floorplan blocks the application Earlier, when users selected certain floors in the live floorplan view in GO, the page turned blank, and the location tree disappeared. After that, it was no longer possible to switch to another floor or location unless the browser cache/cookies were cleared. With the fix, now the affected floors load correctly in the live floor plan. The page no longer goes blank, the location tree remains available, and users can freely switch between floors and locations without needing to clear their browser cache or cookies. | |
GO | Fix for missing building photos An issue was identified where building photos were not visible in the GO, even though the images were available in the IWMS. This was caused by an internal image processing issue that prevented certain photos from being updated and displayed. The issue has now been resolved, and building images are correctly displayed in the app. | |
GO | Notification translation fix An issue was identified where the labels “All,” “Read,” and “Unread” in the Notifications section were not translated to French unless the language was manually reselected from the profile settings. This issue has now been fixed, and the labels are correctly displayed in French based on the selected language settings. | |
Studio | Fix for sensor device batch import failure An issue was identified where batch importing sensor devices via Excel resulted in errors. When the file contained rows with incorrect configuration, the entire import process failed. This issue has now been fixed. The system handles incorrect rows more gracefully, preventing the entire import from failing due to configuration errors in individual entries. | |
Studio | SP metadata download issue An issue was identified where users were unable to download the SP Metadata file in the SAML SSO configuration screen. This was caused by a UI-related problem in the download process. The issue has now been fixed, and users can successfully download the SP Metadata file. | |
Studio | Fix for invalid characters in role names An issue was identified with role name restrictions, where certain special characters were allowed in role names, potentially leading to inconsistencies and configuration issues. Additionally, the UI did not properly restrict or validate unsupported characters during role creation. This has now been improved by enforcing validation rules for role names on the UI. Going forward, role names can only contain letters (uppercase and lowercase), digits, dots (.), spaces, parentheses (), hyphens (-), and underscores (_). Unsupported characters will no longer be allowed when creating or updating roles. Existing roles containing unsupported characters have been reviewed and adjusted wherever necessary to ensure consistency and system stability. | |
Device Control | Improved bulk configuration performance in device control An issue was identified where users were unable to perform Bulk Configuration from Device Control, resulting in a 405 Gateway error. This occurred due to performance delays when processing a large number of rooms, floors, and reservable resources, which caused the request to time out. The processing logic has now been optimized to handle large data volumes more efficiently. As a result, bulk configuration completes successfully without timeouts or server errors, providing a smoother and more reliable experience. |