AMGiNE – Features Released to Production
- Travel Policy: Feature to Auto assign ‘Trip Total Flight Price’ from ‘Flight Price LLF’ calculation
- When policy includes ‘Flight Price LLF’ plus a dollar amount, the calculated LLF (lowest logical fare) is automatically assigned as the Maximum ‘Trip Total Flight Price’ value.
- This feature allows dynamic assignment of Maximum budget based on the itinerary requested and the LLF calculation.
- White Label Form: Feature to support Guest Traveler workflow
- White Label Form submission requires a user to authenticate via a code sent to their email.
- Current profile system expects a valid GDS traveler profile for processing
- Introduced a mechanism to allow re-routing to guest flow when a traveler profile is not available.
- This feature will allow known travelers to submit requests and then provide their personal information (name/DOB etc.) in our JENi check out screen.
- Cvent: Feature to support Travel Arranger Registration Type
- When a travel arranger is booking on behalf of one or more other travelers in Cvent, they choose a Travel Arranger registration Type.
- The Cvent registration is generated with the Travel Arranger as the primary attendee plus one or more guests.
- The travel arranger does not require flight options for themselves.
- Amgine now supports this scenario to collect the flight itinerary information and exclude the Travel Arranger from the flight itinerary request.
- API Travel Policy: Feature to consume Policy Rules with Trip Request
- Feature to allow Travel Policy rules to be dynamically defined in the API call to our service.
- This feature allows Amgine API users to manage policy rules internally and not depend on the Amgine Policy rule set.
- For API users this eliminates the need to create or update policy rules in Amgine.
- API Intent Only option: Feature to allow submission of ‘Intent Only’ trip requests
- This feature allows submission of requests to be processed as ‘Intent Only’.
- Intent only requests allow a TripID to be created without triggering content fetch from the GDS.
- In conjunction with Direct to Traveler flow, a link to the JENi traveler experience can be generated and sent to the traveler .
- The traveler is directed to the Modify screen in JENi with the expected itinerary pre populated .
- Traveler can make changes or additions to the itinerary, trigger content fetch and proceed to booking.
- Using this method API users can defer content fetch until the traveler triggers the search. This provides fresh results on the initial search.
- For groups where deviations are common, it allows the user the flexibility to make changes prior to content fetch.
- Database: Added airport code SWO
- Added airport code SWO – Stillwater Regional Airport, Oklahoma.
- Amadeus: Feature to include S coded (service elements) lines
- All Amadeus profile move commands now include the S coded lines of the profile to be added to the PNR.
- Amadeus: Feature to update name field reference information
- Custom fields now support changes to the reference information associated with an Amadeus name field.
- Amadeus: Issue Resolution – Middle Name
- Resolved an issue with Amadeus PNR creation where passenger middle names failed to be added to the name field of the PNR.
- API Amadeus: Issue Resolution – Guest Workflow fallback
- Resolved an issue where requests that did not have a traveler profile defined would fail.
- When a traveler profile is not available in the in API call we default to Guest workflow to complete the PNR.
- Amadeus: Issue Resolution – Multi passenger bookings
- Resolved an issue where trip requests with multiple passengers would cause PNR creation to fail.
- Amadeus: Issue Resolution – Queue Placement fails to use the correct category
- Resolved an issue where PNR queue placement failed to identify the correct category.
- PNR Creation: Issue resolution – date error when adding Ticketing/Timelimit entry
- Resolved an issue with date calculation due to timezone error.
- Added logging for improved internal monitoring.
- White label Form: Issue Resolution – TSA information SSR fails in the PNR
- Resolved an issue where Trips submitted via White Label form failed to add the TSA SSR (DOB/Gender) information to the PNR.