Trava
Docs
Trava.co
Back home Scheme elements
Conditions
Сondition is enabled
Condition does not exist
Condition with additional functionality
Exists only if PNR accessibility is enabled

Itinerary (air)

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Airline record locator exists for all segments
Airline record locator is missing
Carrier
Codeshare
Flight number
Reservation class
Routing
Segment status

Airline record locator exists for all segments

Overview

Checks whether the airline record locator is assigned to all segments in the PNR.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Airline record locator is missing

Overview

Checks whether the airline record locator has not been assigned to the PNR within the specified time period.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

test

Use cases

test

Carrier

Overview

Checks whether the specified carrier is involved in the PNR – as a marketing, operating, or issuing carrier.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

This condition checks if the PNR contains a flight operated by the specified carrier (marketing or operating codes can be checked), or if the PNR is priced using the specified issuing carrier.

It includes the following options:

Carrier.jpg

1. Type of carrier
Select the type of carrier to be checked: Any, Marketing, Operating, or Issuing.

Notes:

  • By default, the Amadeus PNR reading web service (PNR_Retrieve) does not return operating carrier information for segments. To include it, set the DSD field in the OfficeID settings to YES (contact your Amadeus manager for assistance).  
  • Even with DSD activated, Amadeus may omit operating carrier data for some segments. To retrieve it, request flight information (DO entry). 
    You can enable the system do this automatically when the PNR is first read, or when segments are added/changed: System settings > Amadeus > General > Read additional information about the segment using the DO command.  
  • Issuing carrier is checked based on the latest valid pricing records (PQ/TST/FF) or tickets. If none are present in the PNR, the condition result will be false.

2. Segments to check
Choose which segments are considered.

For issuing carrier, only two options are available:

  • For any of the segments – at least one issuing carrier must match the entered value.
  • For all segments – all PNR-issuing carriers in the PNR must match the entered value.

3. Carrier code field
Enter the IATA code(s) of the carrier to be checked. Multiple codes can be separated by commas.

Notes:

  • If Operating carrier is selected, this field can be left empty. In this case, the system will check whether the PNR contains any codeshare flight.
  • For more advanced codeshare checks, use the Codeshare condition.

4. Carrier tags
Instead of entering carrier codes, you can select carriers by tag.

How to use:

  1. Create a tag: System settings > Tags > Carrier tags.
  2. Go to Settings > Carriers. Assign this tag to the relevant carriers.

When you select this tag in the Carrier condition settings, all carriers with this tag will be checked.

5. Future segments only
When enabled, only segments with a future departure date are checked.
This setting takes precedence over the Choose segments option.

Codeshare

Overview

Allows you to check whether the booked segments include codeshare flights.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Flight number

Overview

Checks whether the PNR contains a specified flight number.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

This condition verifies if the PNR includes a segment with the specified flight number. 

The value can be:

  • A 1- to 4-digit flight number (e.g., 157)
  • A combination of a two-character marketing carrier code and a flight number (e.g., SK157)

Multiple values and flight ranges (e.g., 100–200 or SK100–200) are supported.

Reservation class

Overview

Allows you to check whether the PNR contains the specified booking class.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

This condition checks whether the PNR contains a segment with the specified reservation class. 

The value can be a single-letter class designator (for example, K or Z), or a combination of a two-character marketing carrier code and a class designator (for example, SK-K). 

In the latter case, the condition also verifies that the segment with this class is operated by the specified marketing carrier.

Use cases

In this example, the PNR contains highlighted segments.

Reservation class.jpg

The result of the condition check varies depending on the entered search value.

Search valueResultExplanation
NTrueThe PNR contains a segment with reservation class N.
AY-OTrueThe PNR contains a segment with reservation class O, and the marketing carrier is AY.
SK-OFalseThe PNR contains segments with reservation class O, but their marketing carrier is not SK.

Routing

Overview

Allows you to check the routing type of the booked itinerary and whether specified cities, airports, or countries are included in it.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Segment status

Overview

Allows you to check whether one or all segments of the reservation have the specified status.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Itinerary (hotel)

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Hotel supplier

Hotel supplier

Overview

Allows you to check whether the processing history contains an event with the specified code.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

Useful for verifying whether a specific event occurred during PNR processing.

Itinerary (car)

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Car supplier

Car supplier

Overview

Test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

TEST

Use cases

Test TEST

TestTestTest
  • Test
  • Test
  • Test

Processor

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Events in the processing history
The active instance is processed in a different scheme
Variable contains value

Events in the processing history

Overview

Allows you to check whether the processing history contains an event with the specified code.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Mid-office processing
Description

Useful for verifying whether a specific event occurred during PNR processing.

The active instance is processed in a different scheme

Overview

Allows you to check whether the PNR processed by the current scheme is also being processed by another scheme.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Mid-office processing

Variable contains value

Overview

Allows you to check whether a user-defined variable has the specified value.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Mid-office processing

PNR elements

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Document Itinerary remarks
E-mail identified
Form of Payment
Office or user
OSI messages
Passenger age
Passenger age (range)
Passenger name length
Remarks
Seating exists
SSR messages
Suitable age for YTH type
Ticketing field

Document Itinerary remarks

Overview

Allows you to check whether the PNR contains a document itinerary remark (DI.FT or DI.AC) with the specified value.

Applicable to GDS

1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

E-mail identified

Overview

Allows you to check whether an email element (APE, PE, or EM) is present in the PNR and has the specified value.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Form of Payment

Overview

Allows you to check whether the FOP (Form of Payment) element is present in the PNR and has a specified value.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Office or user

Overview

Allows you to check the agent ID that created the PNR, the office where the PNR was created or ticketed, and the current owning office.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

OSI messages

Overview

Allows you to check whether the PNR contains an OSI message with the specified type, text, and status.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Passenger age

Overview

Allows you to check whether the age of one or all passengers is greater than or less than a specified value.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Passenger age (range)

Overview

Allows you to check whether the age of one or all passengers falls within a specified range.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Passenger name length

Overview

Allows you to check the length of the full name of one of the booked passengers.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Remarks

Overview

Allows you to check whether the PNR contains a remark with the specified text value.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Seating exists

Overview

Allows you to check whether at least one passenger has an assigned seat.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

SSR messages

Overview

Allows you to check whether the PNR contains SSR messages with the specified status and/or text.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Suitable age for YTH type

Overview

Allows you to check whether the reservation is booked or priced for an adult, child, infant, or any other specified passenger type.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing

Ticketing field

Overview

Allows you to check whether the ticketing field of the PNR contains the specified text value.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Mid-office properties

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Booking contains product
Booking is paid
Mid-office field contains value

Booking contains product

Overview

Allows you to check whether the mid-office order contains products with the specified codes.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Mid-office processing

Mid-office field contains value

Overview

Allows you to check whether the mid-office order contains a field with the specified value.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Mid-office processing

Time

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Event happened
Event time (reservation)
Ticket Time Limit (TTL)
Time before event
TTL outside working days
TTL outside working hours

Event happened

Overview

Allows you to check how much time is left before, or has passed since, one of the following events: ▪ Reservation was created ▪ Original departure commenced ▪ One of the tickets was issued ▪ Travel was completed ▪ First processing attempt by this scheme

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Event time (reservation)

Overview

Allows you to check whether a PNR-related event is within the specified period.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types

Ticket Time Limit (TTL)

Overview

Allows you to check how much time is left before the reservation TTL expires, or whether it has already expired.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Time before event

Overview

Allows you to check how much time is left until one of the following events: ▪ Original departure ▪ First upcoming flight segment ▪ First upcoming schedule change ▪ First upcoming non-HK segment ▪ Return travel

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

TTL outside working days

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

TTL outside working hours

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Properties

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Baggage included
Cabin class
Group PNR
Itinerary exists in PNR
NDC reservation
Placed on queue
Rental voucher issued
SFPD/APIS is missing
Split PNR
Tagged as
Types of segments

Baggage included

Overview

Allows you to check whether the reservation is priced with a fare that includes baggage.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing

Cabin class

Overview

Test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

TeSt Test

Use cases

Test

Group PNR

Overview

Allows you to check whether the reservation processed by the scheme is a group reservation.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR redirector
Description

Allows you to check whether the reservation processed by the scheme is a group reservation.

Use cases

Allows you to check whether the reservation processed by the scheme is a group reservation.

Itinerary exists in PNR

Overview

Allows you to check whether the PNR contains at least one active flight segment.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

Allows you to check whether the PNR contains at least one active flight segment.

Use cases

Allows you to check whether the PNR contains at least one active flight segment.

NDC reservation

Overview

test

Applicable to GDS

1A, 1G

Applicable to scheme types
PNR processing
PNR pricing
Description

test

Use cases

test

Placed on queue

Overview

Allows you to check whether the PNR is currently placed in the specified queue or has a future queue placement request entered.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

Allows you to check whether the PNR is currently placed in the specified queue or has a future queue placement request entered.

Use cases

Allows you to check whether the PNR is currently placed in the specified queue or has a future queue placement request entered.

Rental voucher issued

Overview

Applicable to GDS

1A

Applicable to scheme types
PNR processing
PNR pricing

SFPD/APIS is missing

Overview

Allows you to check whether the SSR DOCS in the required format has not been entered for at least one passenger.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing

Split PNR

Overview

Allows you to check whether the reservation processed by the scheme is a split reservation.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing

Tagged as

Overview

Allows you to check whether the processing instance is tagged with the specified tags.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
EMD processing
Mid-office processing

Types of segments

Overview

Allows you to check whether the PNR contains a booked segment of the specified type: air, hotel, car, retention.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Schedule changes

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Cancelled flight without new alternative
Coupon route differs from segments
Coupons and segments do not match
Minimum connecting time is valid for all segments
PNR contains unresolved schedule change
Routing has changed
Schedule time has changed by
Similar segments exist

Cancelled flight without new alternative

Overview

Allows you to check whether the PNR contains an unresolved schedule change where the airline has cancelled a flight without offering an alternative.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR redirector

Coupon route differs from segments

Overview

Allows you to check whether the route of any ticket coupon differs from that of the corresponding segment.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Coupons and segments do not match

Overview

Allows you to check whether ticket coupons differ from the corresponding PNR segments in the specified parameters.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Minimum connecting time is valid for all segments

Overview

Allows you to check the MCT (Minimum Connecting Time) for the entire booked itinerary using the GDS built-in command.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing

PNR contains unresolved schedule change

Overview

Allows you to check whether a PNR contains unresolved schedule changes from the system's point of view.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR redirector

Routing has changed

Overview

Allows you to compare the current PNR segments with the originally booked segments or with the segments before the last unaccepted schedule change, and check whether the route has changed.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Schedule time has changed by

Overview

Allows you to check whether the PNR contains an unresolved schedule change that meets the specified criteria.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR redirector
Description

This condition works with schedule changes received in the PNR from the carrier. Airlines set rules for handling such changes and may require agents to reissue tickets in the case of significant modifications. Agents can automate schedule tracking using this condition.

Schedule time has changed by.jpg

Use cases

The condition searches for unresolved schedule changes in the PNR. If any are found, it allows the agent to:

  • Check how much the schedule has shifted for the affected segments
  • Detect date changes, even those caused by minor schedule adjustments
  • Examine the history of schedule changes

How the system detects changes

Schedule changes are made by the carrier in the PNR using segment statuses (e.g., TK and UN).
These changes can vary:

  • multiple updates to the same segment
  • one segment replaced by another
  • one segment split into several
  • multiple segments replaced, etc.

The system analyzes the segment change history, tracks status updates, and identifies unresolved statuses.

When analyzing a schedule change for a segment, the system compares the current segment data with the historical data and checks it against the parameters defined in the condition.

⚠️ If the system detects manual intervention and the changes were accepted by the agent or the airline, then the schedule change will not be identified. In this case, the condition will return as Fail.

Suggestion: Use the PNR contains unresolved schedule change condition in the previous step to ensure the Schedule time has changed by condition is triggered based on changes already detected by the system.

If the system is unable to find the previous segment for comparison (e.g., the agent deleted it manually, or a UN status was received without an alternative), the schedule change will be detected, but the time difference cannot be calculated.

This behavior is controlled by the setting:

If the system is unable to calculate the time change value due to the absence of the previous segment, consider the result as [True|False]

⚠️ Choose the result that matches the branch where agent attention is required.  

Schedule change check

Specify in the condition the number of minutes that qualifies a schedule change as significant and requires the agent's attention. Configure the parameters using the following settings:

The new flight time is more/less than […] hours before /or/ after the original time.

The values mean:

  • before or after – the time shift occurred in either direction relative to the original time
  • before – the new time is earlier than the original
  • after – the new time is later than the original

If the The condition is met when date changes setting is enabled, the condition will return True when a date change is detected, and it will not evaluate how much the time has shifted (earlier or later).

This setting is useful when you need to detect date changes even in cases of minor schedule adjustments.

💡 Use the MORE setting to track only significant schedule changes that require attention.  

Examples

Let’s examine how the system behaves with the MORE/LESS settings. 

See example:

The new flight time is MORE/LESS than 00:15 hours before /or/ after the original time

Example 1: Departure and arrival times changed by 10 minutes.

Previous segment:

CAI–RMF MS 184 Y 06APR25 08:00–09:20 HK

Current segment:

CAI–RMF MS 184 Y 06APR25 08:10–09:30 TK

Results:

than 00:15 hourbefore or after departurebefore departureafter departure
MOREFalse (1)False (2)False (3)
LESSTrue (4)False (5)True (6)

1 – The new flight time is more than 0:15 hour before or after departure → False (No, the change is 10 minutes, which is less than 15)  
2 – The new flight time is more than 0:15 hour before departure → False (No, the time did not shift earlier)  
3 – The new flight time is more than 0:15 hour after departure → False (No, the shift is only 10 minutes, which is less than 15)  
4 – The new flight time is less than 0:15 hour before or after departure → True (Yes, the change is 10 minutes, which is less than 15)  
5 – The new flight time is less than 0:15 hour before departure → False (No, no shift to an earlier time occurred)  
6 – The new flight time is less than 0:15 hour after departure → True (Yes, the time shifted 10 minutes later, which is less than 15)

Example 2: Departure and arrival times changed by exactly 15 minutes.

Note: A 15-minute schedule change is neither more nor less, but equal (=) to the value specified in the condition. Therefore, the condition will return False in all cases. Please review the results carefully.

Previous segment:

CAI–RMF MS 184 Y 06APR25 08:00–09:20 HK

Current segment:

CAI–RMF MS 184 Y 06APR25 07:45–09:05 TK  

Results:

than 00:15 hourbefore or after departurebefore departureafter departure
MOREFalse (1)False (2)False (3)
LESSFalse (4)False (5)False (6)
  1. The new flight time is more than 0:15 hour before or after departure → False (No, the change is exactly 15 minutes, not more)  
  2. The new flight time is more than 0:15 hour before departure → False (No, it’s exactly 15 minutes)  
  3. The new flight time is more than 0:15 hour after departure → False (No, the time did not shift later)
  4. The new flight time is less than 0:15 hour before or after departure → False (No, it’s exactly 15 minutes, not less)  
  5. The new flight time is less than 0:15 hour before departure → False (No, 15 minutes is not less than 15)
  6. The new flight time is less than 0:15 hour after departure → False (No, the time did not shift later)
Example 3: Departure and arrival times changed by 30 minutes.

Previous segment:

CAI–RMF MS 184 Y 06APR25 08:00–09:20 HK

Current segment:

CAI–RMF MS 184 Y 06APR25 07:30–08:50 TK

Results:

than 00:15 hourbefore or after departurebefore departureafter departure
MORETrue (1) True (2)False (3)
LESSFalse (4)False (5)False (6)
  1. The new flight time is more than 0:15 hour before or after departure → True (Yes, the change is 30 minutes, which is more than 15)  
  2. The new flight time is more than 0:15 hour before departure → True (Yes, shifted 30 minutes earlier, which is more than 15)  
  3. The new flight time is more than 0:15 hour after departure → False (No, the departure time did not shift later)  
  4. The new flight time is less than 0:15 hour before or after departure → False (No, 30 minutes is not less than 15)  
  5. The new flight time is less than 0:15 hour before departure → False (No, 30 minutes is not less than 15)
  6. The new flight time is less than 0:15 hour after departure → False (No, the departure time did not shift later)
Example 4: The PNR contains multiple changes: both significant and minor.

Previous segments:

MXPDOH QR 128 O 25MAR25 1535 2315 HK

DOHNBO QR1335 O 26MAR25 0225 0735 HK

NBODOH QR1342 O 09APR25 0120 0630 HK

DOHMXP QR 127 O 09APR25 0905 1415 HK

         
Current segments:

MXPDOH QR 128 O 25MAR25 1545 2325 TK  – Departure and arrival times changed by 10 minutes

DOHNBO QR1335 O 26MAR25 0225 0735 HK

NBODOH QR1342 O 09APR25 0120 0630 HK

DOHMXP QR 127 O 09APR25 0715 1225 TK  – Departure and arrival times changed by 1:50 hours

Results:

  • The new flight time is more than 0:15 hour before or after departure True.
    The condition looks for a schedule change that matches the specified criteria, and the change is more than 15 minutes, it will detect it.  
  • The new flight time is less than 0:15 hour before or after departure True.
    The PNR contains a change that matches the specified parameter.
    Important notice: In this case, the system will ignore the significant change.

Suggestion: Use the MORE parameter to track significant changes in the PNR.

If you need to track the LESS parameter, we recommend combining this condition with an inverted condition that additionally checks for a date change.

A condition configured as in the example below will return True only if the change is less than the specified threshold and no date change occurred:

Date check.jpg

Searching for schedule changes that occurred in the past

The Take into account all schedule changes, including historical options, allows you to check all schedule changes that have occurred since the PNR was created, even if there are no current unresolved changes.

Avoid using this settings.jpg

This option is useful for tracking changes when the airline made mass schedule adjustments in the past (e.g., flight cancellations during the pandemic).

By enabling this option, you can consider all changes made to the PNR from the moment of its creation until all segments were removed.

If you need to limit the historical check by date (e.g., if the airline allowed penalty-free ticket refunds for flights canceled before date X), be sure to reflect that in the condition settings.

⚠️ If the checkbox is not selected, but a date is specified, the system will search for PNRs with unresolved schedule changes up to the specified date.

⚠️ Do not use this setting if you only want to work with current unresolved schedule changes that are present in the PNR at the time of processing.

Suggested elements

Preceding elements:

  • Segment status – to check that there are no HX segments in the PNR  
  • PNR has unresolved schedule changes – to verify that the system has detected unresolved changes

Subsequent elements:

  • Accept schedule change – if minor schedule changes are found and it is necessary to update all segment statuses in the PNR

Similar segments exist

Overview

Allows to check if the reservation contains segments similar to the specified parameters.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Ticket

Containing taxes

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Coupon conditions/Arrival city/country

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Coupon conditions/Coupon status

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Coupon conditions/Departure city/country

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Coupon conditions/Fare basis

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Coupon conditions/Flight number

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Coupon conditions/Marketing carrier

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Coupon conditions/Reservation class

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Endorsement

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Event time (ticket)

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

FOP

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Issued in exchange

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Issuing carrier

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Issuing country

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Issuing IATA

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Issuing office

Overview

test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

test

Original FOP

Overview

test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

test

Routing

Overview

test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

test

Tagged as

Overview

test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

test

Use cases

test

Ticket is refundable (invol refund rulesets)

Overview

test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

test

Use cases

test test

Ticket is voidable

Overview

test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

test

Use cases

test

Ticket validity

Overview

test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

test

Use cases

test

Time before ticket event

Overview

test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

test

Use cases

test

Total amount

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Tour code

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Voluntary ticket refund is possible

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Ticket routing has changed

Overview

test

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing
Description

test

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Need to issue EMD for optional services
Non-synchronized ticket
Non-ticketed reservation
Ticket conditions
Ticket coupon status
Ticket is valid for travel
Ticket issued by
Ticketing request exists

Need to issue EMD for optional services

Overview

Allows you to check whether the reservation contains optional services with confirmed status that require EMD issuance.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

Optimization is confirmed if the reservation was rebooked to a lower price:

Booking has been optimized.jpg

▪ using "Find Lower Fare" by changing the booking class
▪ using "Find Lower Fare" or "Start" step by changing the fare basis without changing the booking class
▪ using "Start" step without changing the booking class and fare basis
▪ manually by agent after notification of possible optimization was sent

Non-synchronized ticket

Overview

Allows you to check whether the reservation contains at least one active ticket that could not be synchronized in the GDS.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

Tickets with coupon status VOID, EXCH, RFND, or USED/FLOWN are considered final and will always be treated as synchronized without a synchronization attempt.

Use cases

In this case, the condition will be met because PQ contains the mentioned indicator.

Credit card is not allowed as FOP.jpg

Non-ticketed reservation

Overview

Allows you to check whether any passenger in the PNR has at least one flight segment subject to e-ticketing that is not covered by a ticket coupon.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Ticket conditions

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Ticket processing

Ticket coupon status

Overview

Allows you to check the status of one or more ticket coupons.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

The system will look for the specified fare basis in the pricing records for the processed PNR, as they stored in the system. From the system's point of view, each passenger has an individual pricing record, each of which is populated pricing data from the PQ/TST/FF or from the ticket, if it is issued and valid for flight.

In simple terms, if the PNR is ticketed, system will look for the specified fare basis in the issued tickets, if it is unticketed - in the PQ/TST/FF, if partially ticketed - in the ticket or PQ/TST/FF, whichever is available for the particular passenger.

The condition will be met if the PNR is priced using the specified fare basis. You can use special markup to refine your search.

Sometimes the fare basis may consist of a primary fare code and a ticket designator, e.g. QSALE/ID00, KF0DSC00/TO, VLXESSEVF/VF etc.

GDS web services may return a designator in different ways for both PQ/TST/FF and tickets - sometimes separately, sometimes concatenated, and in the latter case the designator may be also truncated. Please keep this in mind when using the condition.

Farebasis.jpg

Use cases

PNR has a pricing record contains highlighted fare basis codes:

Fare basis.jpg

What will be the result of the check by condition, depending on the entered search value:

– Нужна таблица

Ticket is valid for travel

Overview

Allows you to check whether all PNR tickets have coupons with an active status (Open, Airport Control, Checked-In, Lifted) and associated segments with a confirmed status (HK, TK).

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Ticket issued by

Overview

Allows you to check whether at least one ticket has been issued by an agent with the specified ID.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Ticketing request exists

Overview

Allows you to check whether a ticketing request has been submitted.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing
Description

The action can be triggered by selecting the PNR on the Reservation Processing page and using the Tag with Issue Tickets and Run Now buttons.

EMD

Coupon conditions/Arrival city/country

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing

Coupon conditions/Coupon status

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing

Coupon conditions/Departure city/country

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing

EMD is refundable

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing

FOP

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing

Issue date

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing

Issuing carrier

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing

Issuing IATA

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing

RFISC

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing
Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
EMD conditions
PNR contains issued EMD

EMD conditions

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
EMD processing

PNR contains issued EMD

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing

Errors

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Ticketing error

Ticketing error

Overview

Allows you to check the exact error that occurred when issuing a ticket using the Issue ticket element.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing

Fare

Condition name PNR processing PNR pricing PNR redirector Ticket processing EMD processing Mid-office processing
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
1A 1S 1G
Booking has been optimized
Credit card not allowed as FOP
Fare indicator
Fare basis
Has suggestion to improve the reservation
Currency of the latest PQ/TST/TR/FF
Latest fare change
Lower fare for YTH is available
Lower fare is available
Passenger type
Theoretically possible to reduce total amount
Tomorrow's PNR value prediction
Tour code

Booking has been optimized

Overview

Allows you to check if the reservation has been optimized by the system.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing
Description

The condition will be met if the processed reservation has been optimized by the system. 

Booking has been optimized.jpg

Optimization is considered if the reservation was rebooked to a lower price by one of the following ways:

▪ Using the Find lower fare condition by changing the booking class
▪ Using Find lower fare or Start by changing the fare basis without changing the booking class
▪ Using Start without changing the booking class and fare basis
▪ Manually by agent after notification of possible optimization was sent

Since the condition tracks system profit, it is configured in System settings → GDS Common using the following options:

  • Consider initial fare decrease due to the change of office as system profit
  • Consider continuous fare decrease in the same reservation class as system profit
  • Consider currency rate changes as system profit

Credit card not allowed as FOP

Overview

Allows you to check if the PQ contains a restriction on using credit cards as FOP.

Applicable to GDS

1S, 1A, 1G

Applicable to scheme types
PNR pricing
Description

The condition will be met if the PQ contains an indicator stating that when issuing a ticket, a credit card should not be used as FOP.

Credit card not allowed as FOP.jpg

Use cases

In this case, the condition will be met because PQ contains the mentioned indicator.

Credit card is not allowed as FOP.jpg

Fare indicator

Overview

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector

Fare basis

Overview

Allows to check if the reservation is priced using the specified fare basis.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

The system searches for the specified fare basis in the pricing records of the processed PNR, as stored in the system. From the system’s perspective, each passenger has an individual pricing record, which is populated with pricing data from the PQ/TST/FF, or from the ticket if it has been issued and is valid for the flight.

Farebasis.jpg

In simple terms, if the PNR is ticketed, the system searches for the specified fare basis in the issued tickets. If it is unticketed, the system searches in the PQ/TST/FF. If it is partially ticketed, the system checks either the ticket or the PQ/TST/FF, whichever is available for the particular passenger.

The condition is met if the PNR is priced with the specified fare basis. You can use special markup to refine the search.

Use cases

PNR has a pricing record contains highlighted fare basis codes:

Fare basis.jpg

The result of the condition check varies depending on the entered search value:

Search valueResultExplanation
LNCTrueIf no markup is used, the system searches for a fare basis that contains the search value in any position.
OLNC08S7TrueSame as above, but the search value is fully equivalent to one of the fare basis codes.
"OLNC08S7"TrueIf the search value is enclosed in double quotes, the system searches for the exact value.
"OLNC08F1"FalseSame as above.
"PSELP5"FalseSame as above.
"%M7"TrueThe percent sign (%) represents zero, one, or multiple characters. When combined with double quotes, it can be used to search for a fare basis ending in "M7".
_LNC0__7TrueThe underscore sign (_) represents any single character. It can be used to search for a fare basis using a mask that matches different values.

Sometimes the fare basis may consist of a primary fare code and a ticket designator, e.g. QSALE/ID00, KF0DSC00/TO, VLXESSEVF/VF etc.

GDS web services may return a designator in different ways for both PQ/TST/FF and tickets – sometimes separately, sometimes concatenated, and in the latter case the designator may be also truncated. Please keep this in mind when using the condition.

Has suggestion to improve the reservation

Overview

Allows you to check the method by which PNR can be optimized.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing
Description

This condition is intended to be used after the Lower fare is available condition has succeeded, to determine how exactly the PNR can be optimized.

Has suggestion to improve the reservation.jpg

The condition will be met if the PNR can be optimized by the selected method:

to improve: optimize any way
to rebook: optimize by changing the booking class
to get better fare for: optimize by changing the fare basis without changing the booking class
to split: optimize by splitting one of the passengers to another PNR, where a lower price is available

Currency of the latest PQ/TST/TR/FF

Overview

Allows you to check the currency of the latest pricing record (PQ/TST/TR/FF) of the PNR.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing
Description

To start processing a PNR by a PNR pricing scheme, the system requires that all passengers and segments are covered by valid PQ/TST/FF and if there are multiple PQs/TSTs/FFs, the latest one is selected. 

Currency of the latest.jpg

This condition allows to check if the currency of all or at least one PQ/TST/FF matches the specified one.

Latest fare change

Overview

Allows you to check the amount of the latest fare change.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing

Lower fare for YTH is available

Overview

-

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing

Lower fare is available

Overview

Allows you to check if the reservation can be rebooked to lower price at the time of processing.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing
Description

This condition checks if a lower price is available for the booked itinerary. It may be possible due to changes in seats availability or available fares within the same reservation class. 

Check only, no rebooking.

Equivalent commands: 

  • WPNC – Sabre
  • FXA/R,UP – Amadeus
  • FQBB – Galileo
Use cases

The condition has the following options to search for lower fares:

Lower fare is available.jpg

1. Group of fares within which a lower fare will be searched – public or private. By default – any. 

2. When alternative codes for adult, child and infant are defined, a search for a lower fare will be made for the specified passenger types instead of those actually booked. 

3. Ignore the found optimization if the saved amount is less than the specified value.

4. Ignore the found optimization if the free baggage allowance for the new fare is more restrictive or no free baggage allowance included.

5. Ignore the found optimization if at least one of the new fare basis codes contains the specified value. Can only be applied to fares of the specified airlines.

6. By default, the found optimization will be ignored if the PNR contains booked optional services, since the optimization will cause them to be lost and will need to be requested again. When this option is enabled, the PNR will be optimized despite optional services.

7. If a brand modifier is specified in the pricing command used to create the original pricing record, the system will always search for a lower fare using the same brand, regardless of this option. 

If a brand modifier is not specified and this option is enabled, the system will search for a lower fare using the brand that was identified for the original pricing record by Trava. Identification is performed in various ways at the beginning of processing and is not guaranteed, as it is limited by the capabilities provided by the GDS.

8. List of PCCs/OIDs that will be used to search for a lower fare. The system will switch processing context to each specified PCC/OID, read the PNR and then search for a lower fare within this PCC/OID. To add an office to the list, it must first be added to Offices and marked as operational.

9. List of ticketing PCCs to use when a PQ is created in a non-ticketing PCC during optimization.
If the non-ticketing PCC (from the list in item 8) is used, it must be paired with a ticketing PCC.
Ticketing PCCs are selected from this list. If the list is empty, the system will use any ticketing PCC available in the given GDS.

To see how the system performed the preliminary calculation for potential optimization, open the processing history.

Passenger type

Overview

Allows you to check if the reservation is booked or priced for adult, child, infant or any other specified passenger type.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR processing
PNR pricing
PNR redirector
Description

This condition allows us to check if the reservation is booked or priced for the specified passenger types. 

Passenger type.jpg

Options

1. Specify whether all or at least one passenger must be of the required type.
2. Specify which passenger type to check: as booked, as priced, or both.
3. Specify the required passenger type.

Passenger types for each passenger

  • As booked – the type assigned to a passenger regardless of PQ/TST/FF and its status. By default, this is considered adult, unless otherwise specified by a name remark.
  • As priced – the type assigned to a passenger according to the fare applied in the associated PQ/TST/FF. This may differ from the as booked type.

Required passenger type

  • Generic (adult, child, or infant)
  • Exact type code (any valid passenger type code such as YTH, ITX, VFR, etc.)

When a generic type is specified, the actual passenger type is converted to one of the three basic types: adult, child, or infant.

Example:

  • ITX (Individual Inclusive Tour Adult) is treated as adult
  • VFN (Visit Friends/Relatives Child) is treated as child

As a result, if a PNR is priced using ITX fares, and the condition checks for adult passengers, the condition will be met.

Theoretically possible to reduce total amount

Overview

Allows you to check the possibility of rebooking to lower price irrespective of seats availability.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing
Description

The condition searches for the lowest applicable fare for the booked itinerary, regardless of seat availability. 

It allows you to verify whether the RBDs you have booked make it possible to obtain the lowest fare.

Theoretically possible to reduce total amount.jpg

The condition returns False if the lowest price is already booked and the PNR cannot be optimized.

Equivalent commands:

  • WPNCS – Sabre
  • FXL – Amadeus
  • FQBA – Galileo

Tomorrow's PNR value prediction

Overview

Allows you to price the PNR for the following day and check whether the price (total or per passenger) has increased or decreased by the specified amount.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing
Description

Price changes may result from exchange rate fluctuations or the expiration of the applied fares.

This condition can help determine whether the ticket should be issued before the end of the day or if the search for a lower fare can continue the next day.

Tomorrow's PNR value prediction.jpg

Tour code

Overview

Checks if the PNR is priced using a fare with a specified tour code or if at least one ticket was issued with it.

Applicable to GDS

1A, 1S, 1G

Applicable to scheme types
PNR pricing
Description

Tour code.jpg

Use cases

In this example, the PNR is priced with the tour code ZZVFR2ZZ:

Tour code.jpg

The result of the condition check varies depending on the entered search value:

Search valueResultExplanation
ZZTrueIf no markup is used, the system searches for a tour code that contains the search value in any position.
ZZVFR2ZZTrueSame as above, but the search value must fully match the tour code.
"ZZVFR2ZZ"TrueIf the search value is enclosed in double quotes, the system searches for the exact value.
"TOGR5"FalseSame as above.
"%ZZ"TrueThe percent sign (%) represents zero, one, or multiple characters. When combined with double quotes, it can be used to search for a tour code ending in "ZZ".
ZZVFR_ZZTrueThe underscore sign (_) represents any single character. It can be used to search for a tour code using a mask that matches different values.