Deem Enhancements for 2024.5.2 Executive Summary  

Deem continues to improve our site administrator and agency experiences with key enhancements that help corporations and TMCs manage the travel buying process.

Check out the details on these Deem updates below!

Regards,

Your Deem Product Management Team 

About the Release Notes  

Deem release notes provide useful technical information about the latest release. For each release, the notes provide:

• A high-level description of the release, including major changes and enhancements

• Instructions to help you get started with set-up and administration (when applicable)

Feature Enhancements

Ticket Exchange Functionality 2024.5.2 Release

Ticket Exchange functionality for non-ATE users is introduced to New Deem with 100% parity with the Classic experience.  

• Validated and Non-Validated tickets are supported for Sabre, Apollo, Worldspan, and Amadeus customers 

• Database identifier introduces to signify if a booking was made on New or Classic Deem  

New Features 

Android and New Deem Desktop

Global Alerts

Alerts configured internally by Deem will display alerts for system maintenance or other issues and updates that impact all customers. 

iOS 1.86 Release

Passport UI

UI updates added to the passport section during the checkout process 

• Passports will now show in a new Documents section along with Known Traveler Numbers and Redress  

• User can edit an existing passport  

• UI will highlight if the passport is expired

Bug Fixes

2024.5.2 Release

• DOT link for insecticides warning on international air travel has been updated to the new link. 

• Site card is available to select for default form of payment for rental car. Resolved.

• Cosmetic fix to the Classic UI. Resolved.

• Unused Ticket Upload result emails are now sent when the job is triggered from the superdomain level. Resolved. 

• Custom fields accept 4000 UTF-8 characters and UI messages this accordingly. Resolved.

• Defensive coding to guard against ghost PNRs. Resolved.

iOS

• Trip objective custom field value was writing incorrectly to the PNR. Resolved.