Source PNR Editing and Error Handling

The application automatically reads text from the Clipboard at startup. The recommended way to initiate a group booking is to copy the email or other message containing the source PNR to the clipboard, then launch Group Processor using the #GRP Quick Command in Smartpoint. You can refresh the Input Data text box at any time by pressing the Load PNR from Clipboard button

Note: It's not necessary to select the exact PNR section from the email. However, the clipboard text must contain only one group booking.

As soon as text is loaded, the application parses the source PNR and populates the following non-editable fields automatically:

• Name List

• Nbr of Pax

• Vendor Locator

• Group Name

• Flight List

Error Handling

If the parser detects any issues, the green OK indicator is replaced with a list of errors, and the Process Booking button is disabled.

The Input Data box can be edited directly using standard keyboard functions (e.g., Ctrl+A, Ctrl+X, Ctrl+C, Ctrl+V). All characters are automatically converted to uppercase to improve readability. Edits are evaluated in real-time, and errors are updated immediately.

Possible Sources of Errors:

• Corrupted or scrambled text in the source PNR

• Missing Vendor Record Locator

• Mismatch between the number of passengers and the passenger list or flight segment bookings

• Flight segments not in HK (confirmed) status

• Flight departure date is more than 335 days in the future

• Flights with invalid data (these are ignored, but at least one valid flight is required)

• Duplicate passenger names in the PNR

• Passengers missing a first name and/or gender

If more than three parsing errors are encountered, the input is considered invalid and likely not a proper PNR.

PNR Parsing Logic Description

The Group Processor follows a structured parsing logic to extract relevant booking data from the source PNR:

• The program begins parsing by searching for the Vendor Record Locator, which marks the start of the PNR.

• Passenger and flight details are extracted using regular expressions for accurate pattern matching.

• Duplicate passenger names are identified, reported as errors, and highlighted in the Input Data field.

• Passengers missing a first name and/or gender are also flagged as errors and highlighted.

• Infants are detected and extracted from parentheses in the passenger list (supported only for 1A PNRs).

• For each flight segment, the parser validates:

• • Number of booked seats

  • Flight status (must be HK)

  • Departure date, which must be within 335 days

• Non-flight segments such as ARNK are ignored and can remain in the input without issue.

• The parser allows for one missing index in the flight list numbering without error.

• If a flight is not recognized by Galileo, it is still processed and booked using the itinerary and timing information from the source PNR.

• The program correctly handles flights with non-standard arrival dates, including:

• • Next-day arrivals

  • Previous-day arrivals

  • D+2 (two days later)

Note: Grouping of surnames into family blocks has been discontinued as of version 1.6.

Identical Passenger Names and Missing First Names Treatment

The Galileo™ GDS does not support duplicate names within a group booking, and requires each passenger to have a first name (or gender). Therefore, the Group Processor performs a validation check on the passenger list:

• Duplicate names are detected and highlighted in the source text.

• Missing first names or gender are also flagged.

• If such issues are found, the Process Booking button is disabled until corrections are made.

To proceed, the names must be manually corrected in the Input Data box.

Example of errors:

• Duplicate passenger names

• Passengers without first names or gender

• Missing mandatory Phone Contact (if configured as required in Setup)

These issues are all displayed clearly in the interface and must be resolved before booking can continue.

Flight Data Error Treatment

The application automatically detects and highlights errors in flight segment data during PNR parsing. The screenshot below illustrates how such issues are displayed and handled:

Examples of Detected Flight Errors:

• Flight OK 101 – Invalid flight status (HL instead of required HK)

• Flight OK 102 – Mismatch in passenger count (2 instead of expected 3)

• Flight OK 103 – General error in flight data formatting

• Flight OK 104 – Departure date exceeds the allowed booking window (more than 335 days ahead)

In addition:

• The ARNK segment is automatically ignored and does not affect processing.

• The application tolerates a missing flight index (e.g., missing index 8 between OK 103 and OK 104) without failing the entire PNR.

Important: If no valid flight segments are detected after parsing, the group booking is blocked, and the Process Booking button remains disabled.