This is an old revision of the document!
Conditions
Available in scheme types:
Mid-Office
Non-pricing
PNR redirector
Pricing and Ticketing
Ticket processing
With conditions you can control what action to take next based on booking elements such as price, fare, itinerary, segment status, ticketing time limit, remarks and much more.
Example where it checks if a remark with the text XYZ exists in the booking. If the remark exists then no action will be taken and the scheme finishes, otherwise in this example it adds the remark and then finishes.
Category | Subject |
Itinerary | Airline record locator exists for all segments |
Airline record locator is missing | |
Carrier | |
Flight number | |
Reservation class | |
Routing | |
Segment status | |
Processor | Variable contains value |
PNR elements | Form of Payment |
Office or user | |
Passenger age | |
Passenger name | |
Remarks | |
Seating exists | |
SSR messages | |
Ticketing field | |
Mid-Office properties | Booking contains product |
Booking is paid | |
Mid-office field contains data | |
Time | Event happened |
Event time | |
Ticketing Time Limit | |
Time before event | |
PNR properties | Baggage included |
Itinerary exists in PNR | |
Placed on queue | |
SFPD/APIS is missing | |
Tagged as | |
Types of segments | |
Fare | Credit card not allowed as FOP |
Farebasis | |
Has suggestion to improve the reservation | |
Latest fare change | |
Lower fare is available | |
Theoretically possible to reduce total amount | |
Tomorrow´s PNR value prediction | |
Tour code | |
Schedule changes | Coupons and segments do not match |
Minimum Connecting Time is valid for all segments | |
Similar segments exist | |
Ticket | 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 | |
Error | Ticketing Error |
Others | The active instance is processed in a different schema |
QC remark check | Use this separate action if you are looking for a condition that checks remarks for specific characters plus characters based on Regular expression use the QC remark check feature. Note: accessed via the QC remark check action, not via Conditions. |
__