Improvements
Age validation has been added on IBE for roundtrip reservations where passenger type must be changed (CHD->ADT, INF->CHD) for return segment
For an IBE round-trip booking with a child or infant, an age validation process can now be triggered. If a passenger's status changes during the flight period, a pop-up message will appear when saving passenger information, instructing the customer to contact the airline, and the payment of the reservation will be blocked.
The feature is not activated by default as it also requires activation of the newly introduced "PaxType midtrip" parameter by GO7 PSS support / implementation team in the back end settings. If you would like this functionality to be activated for your airline, please contact our Support team or your account manager.
We are still working on the feature to be also applied to the rebooking scenario (delivery expected later this autumn).
Bug fixes
- Child baggage allowance has been fixed to be displayed in the booking confirmation / e-ticket
For reservations where child type passengers were present the baggage allowance was not displayed on the print outs”
This has been fixed and now the baggage allowance for children is also displayed:
- Wrong departure time for some of the multileg flights segments on IBE has been fixed
There was an issue observed on IBE only for multileg flights in certain cases where the departure time of the third leg was incorrectly shown on IBE equal to departure time of the first leg. In particular, this was observed for multileg circle flights. This issue has now been fixed by adding to the code, extracting departure time and additional validation by departure airport.
- In CRS it is no longer possible to bypass the mandatory requirement of inserting date of birth (DOB)
We found and eliminated a gap, which previously allowed users and agents to avoid inserting the date of birth for passengers, when it was set to be mandatory. Previously, it was possible to insert the date of birth in the wrong format (d/m/yyyy, d/mm/yyyy or dd/m/yyyy instead of dd/mm/yyyy), then system allowed user proceeding to the next step in the reservation process, however, the date of birth field in the data base remained empty.
After the issue has been resolved, the system will now display an error message: “Please enter date as either dd/mm/yyyy for Passenger #1“
Comments