Summary of Connector updates in Q3 2024 including versions 2.8.0 & 2.8.1

Exchange Connector 2.8.0

Three bug fixes. One enhancement to help with transition from old connector to new version: if blank resource identity, the resource identity (email address) gets updated with email address from resource mapping.

Timing

• July 26, 2024 pushed to AQ internal (prod)
• July 29, 2024 pushed to CS, RWJF (prod)
• August 8, 2024 pushed to Cassels (prod)
• August 13, 2024 applied to Arch Denver, this was the date their connector was created (prod)
• September 13, 2024 pushed to UPP and QuikTrip (prod)

Jira Tickets

• AQMSC-98 Enhancement to help with transition from old connector to new version, aka "Fidelity Model." If the resource identity (email address) is blank, the resource identity gets updated in the backend with the email address from the resource mapping. See AQMSC-51 for more info about direct access in O365 where reservations are made on behalf of the user (Fidelity Model).
• AQMSC-100 Bug fix related to AQMSC-98. An error was being thrown when editing rooms in the Exchange Console (by removing their email address). The fix allows the email address to be removed.
• AQMSC-102 Bug fix related to AQMSC-98. An error was being thrown when editing rooms in the Exchange Console (by adding or editing their email address) in cases where that room is in a dynamic relationship with a room that has an active reservation. The fix allows the changes in the email address field to be saved.
• AQMSC-110 Bug fix to resolve support ticket AQSUP-279 from RWJF. Reservation update notification emails were being sent to all attendees every hour during the pull for missed events. This was happening because of a specific sequence involving an attendee being an inactive user in Reserve and then the reservation owner becoming an active user, followed by the pull for missed events.

Exchange Connector 2.8.1

Multiple bug fixes plus changes needed to apply "Fidelity Model" where needed. Customers have to be put on 2.8.0 before 2.8.1 can be applied because AQMSC-98 mapping is needed. More detail coming...

Timing

• September 11, 2024 pushed to AQ internal (prod)
• September 13, 2024 pushed to RWJF, Cassels, Arch Denver, UPP, and QuikTrip
• September 23, 2024 planning to start push of this release to all remaining customers

Jira Tickets

• AQMSC-76 Tech ticket for Veracode security flaw (use of broken/risky cryptographic algorithm)
• AQMSC-78 Enhancement for UPP and other customers concerned about sharing the subjects of reservations. When the property store.owner.as.reservation.name is enabled and the Connector picks up the appointment from Exchange, the owner's name is saved as the reservation name. AQMSA-43 covers this in the Add-in.
• AQMSC-90 Bug fix to resolve issue in the Outlook appointment window. The start and end time were displaying the correct time but the incorrect time zone. Now both time zones are correct. AQMSA-70 covers this in the Add-in.
• AQMSC-112 Clone of AQMSC-98 since that code for the Fidelity Model needed to be merged and smoke tested in loginauto and loginqa. Enhancement to help with transition from old connector to new version, aka "Fidelity Model." If the resource identity (email address) is blank, the resource identity gets updated in the backend with the email address from the resource mapping. See AQMSC-51 for more info about direct access in O365 where reservations are made on behalf of the user (Fidelity Model).
• AQMSC-113 Clone of AQMSC-100 since that code for the Fidelity Model needed to be merged and smoke tested in loginauto and loginqa. Bug fix related to AQMSC-98. An error was being thrown when editing rooms in the Exchange Console (by removing their email address). The fix allows the email address to be removed.
• AQMSC-114 Clone of AQMSC-102 since that code for the Fidelity Model needed to be merged and smoke tested in loginauto and loginqa. Bug fix related to AQMSC-98. An error was being thrown when editing rooms in the Exchange Console (by adding or editing their email address) in cases where that room is in a dynamic relationship with a room that has an active reservation. The fix allows the changes in the email address field to be saved.
• AQMSC-116 One of the bug fixes to resolve support ticket AQSUP-275 from QuikTrip. After the 2.8.0 Connector release, the sync was not working in some cases. This happened for the scenario where a placeholder appointment for a recurring series was created (placeholder = without a room), then a room is added to an instance via the Add-in, and some change is made (like adding Teams or attendees). The sync worked after this bug fix was pushed.
• AQMSC-117 Bug fix to resolve support ticket AQSUP-325 from RWJF. Only room-type assets (conference rooms and workspaces) should be mapped in the Connector. The issue here was that the asset was in a non-room category (equipment), which caused an error to be thrown. The error caused the resource mapping sync to stop at that row. The fix for this removes the mapping for non-room assets so that an error is no longer thrown and the mapping continues as expected.
• AQMSC-119 One of the bug fixes to resolve support ticket AQSUP-275 from QuikTrip. When a user canceled the room reservation, waited for the sync and then added a different room, the reservation was getting rejected by Reserve (resulting in a rejection email). The fix for this involved a new reservation being created with a new confirmation number.
• AQMSC-120 Bug fix to resolve support ticket AQSUP-359 from RWJF. This bug was introduced when the sync with the Add-in was added. The Connector got ‘America/New York’ (the standard IANA time zone) from Graph API instead of ‘Eastern Standard/Daylight Time’ (Microsoft time zone) To replicate the property phoenix.events.processing.delay must be set to a bigger value, enough seconds to have time to open the attached ICS and add it to your calendar. The fix is to ignore meetings with such timezones: ‘America/New York’ (the standard IANA time zone).
• AQMSC-121 Bug fix to resolve support ticket AQSUP-367 from Arch Denver. A room having an apostrophe in its name could not be edited in the Exchange Console. The fix allows such rooms to be editable (user can modify the email address field).
• AQMSC-123 This bug never made it to prod, QA found it while testing AQMSC-119. The issue occurred in the following scenario: In the web application, the user cancels a multipoint reservation (event). When opening the appointment in Outlook, one of the rooms remained in the appointment. The fix removed all rooms from the appointment.

Exchange Add-in 1.5.2

See the Add-in released on September 13, 2024 in Jira for details. More info coming to describe changes related to Fidelity Model...