Introduction

For release 16.01, ameliaRES has undergone significant changes to how passengers are stored and handled.

Summary

Passengers will now be unique for all reservations.  When a passenger is added to a reservation, their information will be stored in a new Passenger record on that reservation.  Updates to this Passenger will only affect the reservation in question.

This change eliminates instances where an update to a passenger’s information will affect reservations in the past.

Functional Changes

Reservation Passengers

• Every passenger on every reservation will have a unique Passenger record.
• Updating passenger information on a reservation will affect only that reservation.  The prompt warning that existing reservations will be affected has been removed.
• If a User Profile is used, the passenger information will be copied from the User Profile to the reservation.

Passenger Search

• Passenger Search (Desktop and IBE) for reservations will first search User Profiles (if enabled).
• A business rule will dictate if Passenger records will also be used in the search.
  • If enabled, the search will search Active/Denied Passengers.
    • It will search Passenger records on non-expired reservations who have either an email, home phone, business phone, mobile phone, or notes.
    • The search will return one option for each unique Passenger.
      • If a passenger’s information is identical on two different reservations, one option will be returned.
        
      • If a passenger’s information is different between two reservations (e.g. different addresses), it will return two options, one for each address.
    • If multiple Passenger records are found, they will be ordered from most to least recently updated.  The Passenger who had their information entered/updated most recently will appear first in the list.
  • If not enabled, Passenger records will not be searched and only User Profiles can be returned.
    
• Passenger Searches can be done with or without Exact Match.
  • Exact Match
    • Searches can only return User Profiles OR Passenger records, not both.
      
    • If User Profiles are found, they are returned and the search ends.  Passenger records will not be searched and none will be returned.
    • If no User Profiles are found, Passenger records are searched.  If Passenger records are found, they are returned.
    • The IBE uses Exact Match only.
  • Non-Exact Match
    • Searches can return both User Profiles AND Passenger records.
      
    • User Profiles are searched.  If User Profiles are found, they are returned.
    • Passenger records are searched regardless if User Profiles are found.  If Passenger records are found, they are returned.
• The search will return up to 500 unique records.
• Searching for passengers in the Passenger utility and when assigning vouchers will return all Passenger records that fit the search criteria.  If there are two identical records, they will still both be returned.
  

ameliaRES Desktop

• The search fields have been expanded to now include Last Name, First Name, Email, Phone, Mobile, and Loyalty Number.  At least one field must have a value to perform a search.
  
• Exact Match is defaulted to on.
• If the Loyalty Number is used, then all other search fields are ignored and Exact Match is always enforced.
• If a record is chosen from the search, the information from that record is copied into the passenger fields.  The user can then edit any information required.  Upon save, a new Passenger record is created.

ameliaRES Web

• No changes are needed to the ameliaRES Web interface to support the new search.
• As always, the search is only available to logged in agents.

Passenger Utility

• The Passenger utility in ameliaRES Desktop will no longer allow edits to passenger data.  Passengers must be updated directly on the reservation.
• The utility will only allow for viewing Passengers and setting them to Activated, Deactivated or Denied.  Deactivated removes the records from passenger searches.  Denied adds the passenger to the internal blacklist (if enabled).

ameliaRES Desktop

• The Add button has been removed.
  

Companies

• Passengers are no longer tied to companies.

ameliaRES Desktop

• The Passenger tab of the Company utility screen will no longer exist.  The associated permissions will be removed in a follow-up release.
  
• The Company Info prompt during booking creation no longer includes passengers.
  
• The company-related functions on the res pax screen have been moved to their own screen.  The screen is launched by a button which is featured on the reservation passenger screen as well as the main reservation screen.
  

User Profiles

• For public bookings, the IBE will attempt to automatically associate Passengers to User Profiles.
  • Passengers are linked to a User Profile if a valid Loyalty Number is entered.
    
  • If a Loyalty Number is not entered, the system will search for a User Profile that matches the passenger’s name and email address.  If found, the Passenger will be linked to the User Profile.
• For agency bookings, a business rule will dictate if the IBE will attempt to associate Passengers to User Profiles.
  • If enabled, the system will search for a User Profile that matches the passenger’s name and email address.  If found, the Passenger will be linked to the User Profile.
    
  • If disabled, Passengers will only be linked if a valid Loyalty Number is entered.