Release Features

New Features and Capabilities

No new features have been introduced in this release.

Enhancements

No new enhancements have been introduced in this release.

Fixes

A brief description of the fixes which are getting release is below.

Fix #1

ItinReshop-Requote

While requoting a held booking, NDC ItinReshop-Requote API response is not returning the marketing name of the relevant flights. This fix on the ItinReshop-Requote API will enable it to return the marketing name of the relevant flights and selling class.

Fix #2

OrderViewRS

An agent reported that while trying to perform a bag purchase via the OrderChange API, the OrderView response returns incorrect flight reference and is causing the issue at their end. This fix on the OrderView response is to return the same flight reference in flight list which was returned in the flight item.

Fix #3

FlightPriceRQ

Whenever an agent with both CUG code and Amadeus a/c. code sends a FlightPrice request, NDC is returning 304 error. FlightPriceRQ return response when CUG ID is removed.

This fix on the FlightPriceRQ API will enable it to return the flight price response even if both CUG and Amadeus a/c. code is present for the agent.

Fix #4

ItinReshop-Reshop & ItinReshop-Reprice

While trying to perform a change booking for fully flown PNR, reshop and reprice API’s are displaying different error messages in the response. This fix on the ItinReshop-reshop and ItinReshop-reprice operation will enable it to return same user friendly error message in response in case change booking is tried for fully flown PNR.

Fix #5

SeatAvailabilityRS

For a fare which is eligible for free seats, the SeatAvailabilityRS is not returning free seats for cases where agents do not have a BACCI code. This fix on the SeatAvailabilityRS will enable it to return free seats in case agents does not have the BACCI code but fare is eligible for free seats.

Known Issues and Problems

NWDC 3483 – Segment Number Not Valid 

 issue in OrderCreateRQ  on certain routes you may get  Error Segment Number Not Valid     

Work around:

Please chose another route for testing – we are working on this issue and will update this section once we know the release date