Airlines can define additional configuration rules for the Manage Your Booking (MYB) flow servicing options using MYB Rule Sets. The supported servicing options are:

• exchanging
• cancelling
• changing passenger details
• upgrading a flat fee

Service Options must be configured as available in order for the rules to be applied.

The MYB Rules feature makes it possible to fine-tune the IBE's responses to requests for exchanges, refunds, and other MYB services. Setting up rules successfully, however, does require some analysis of an airline's needs and some understanding of how the rules will be applied.

A key concept is the rules set. If you look at the names of the rules sets — EXCHANGE_GUEST, CANCEL_GUEST, EXCHANGE_LOGGEDIN, for example, you will see they represent categories of services requested (cancel, exchange, upgrade, or update details) and user status (guest or logged in). Requests for services are matched to rule sets — requests for exchanges by guest users are matched to rules in the EXCHANGE_GUEST rule set, and so on. You can use the filtering capabilities of the rule sets to set up different rules for different services and user statuses.

MYB rules can be combined into sets. Different sets can be configured for booking flows or servicing options. A rule set is an ordered collection of rules and is evaluated in sequence with conjunction logic applied. The evaluation stops at the first rule that results in failure in evaluation.

Within each rule set, individual rules determine the conditions that allow or disallow requests for that rule set. The implementation of rule sets and rules leads to to the following behavior:

• Guest users cannot exchange (this results from the ALWAYSFALSERULE in the EXCHANGE_GUEST rule set).
• Guest users cannot cancel (this results from the ALWAYSFALSERULE in the EXCHANGE_GUEST rule set).

Logged in users can exchange, subject to the limitations established by the rules in the EXCHANGE_LOGGEDIN rules set: the MULTICITYRULE prevents exchanges of multi-city bookings, and the TIERLEVELRULE allows exchanges only if the user is in the platinum or gold tiers — this means that other levels are not allowed to exchange.

This example also illustrates some characteristics of rule sets and rules:

• The basic principle that a rule allows or disallows the servicing option specified by the rule set, according to the additional filtering specified by the rules.
• Some rules are simple allow/disallow rules. In this example, the MULTICITYRULE disallows exchanges on all multi-city bookings, without further filtering
• Some rules take "parameter" values that allow additional filtering. In this example, the TIERLEVELRULE filters the frequent flyer tiers that are allowed to exchange.
• Rules can be set up tas allow/disallow rules. Depending on the situation, one will probably be more efficient than the other. In this example it was easier to specify the two frequent flyer tiers allowed to exchange than to list all the tiers that are not allowed to exchange.
• Another important concept is that any request, not specifically covered by a rule set/rule combination is allowed. Taking a second look at the example implementation we see that:

Rules sets for UPGRADE_GUEST, EDIT_PAX_DETAILS_GUEST, UPGRADE_LOGGEDIN, CANCEL_LOGGEDIN, EDIT_PAX_DETAILS_LOGGEDIN are not established, so any request matching these categories is allowed.

The rules for EXCHANGE_LOGGEDIN prevent frequent flyer tiers other than platinum and gold from exchanging. They also prevent platinum and gold frequent flyers from exchanging multi-city bookings, but there are no other restrictions — outside of multicity bookings, users in the platinum and gold tiers can exchange their bookings freely.

MYB Rule Sets

The MYB rule sets are listed in the following table:

Rule set	Description
UPGRADE_GUEST	A set of rules for upgrading flat fee when the user is a guest user.
CANCEL_GUEST	A set of rules for cancelling and refunding itineraries when the user is a guest user.
CANCELITINERARY_GUEST	A set of rules for cancelling itineraries when the user is a guest user.
CANCEL_UPGRADE_FQT_GUEST	A set of rules for cancelling upgrades from the waitlist when the user is a guest user.
EXCHANGE_GUEST	A set of rules for exchanging itineraries when the user is a guest user.
EDIT_PAX_DETAILS_GUEST	A set of rules for modifying passenger details and editing SSRs when the user is a guest user.
UPGRADE_LOGGEDIN	A set of rules for upgrading flat fee when the user is logged in.
CANCEL_LOGGEDIN	A set of rules for cancelling and refunding itineraries when the user is logged in.
CANCELITINERARY_LOGGEDIN	A set of rules for cancelling itineraries when the user is logged in.
CANCEL_UPGRADE_FQT_LOGGEDIN	A set of rules for cancelling upgrades from the waitlist when the user is logged in.
EXCHANGE_LOGGEDIN	A set of rules for exchanging itineraries when the user is logged in.
EDIT_PAX_DETAILS_LOGGEDIN	A set of rules for modifying passenger details and editing SSRs when the user is logged in.
ANCILLARIES_MTO_GUEST	A set of rules for the Modify Trip Options booking flow and a guest user. Note: The ancillaries MTO flow includes The (Undefined variable: MyVariables.AncillaryPage) and the (Undefined variable: MyVariables.Seatspage).
ANCILLARIES_MTO_LOGGEDIN	A set of rules for the Modify Trip Options booking flow and a logged-in user. Note: The ancillaries MTO flow includes the (Undefined variable: MyVariables.AncillaryPage) and the (Undefined variable: MyVariables.Seatspage).
SEATS_MTO_GUEST	A set of rules for the seats flow when the user is a guest user. The seats MTO flow includes the (Undefined variable: MyVariables.Seatspage) only.
SEATS_MTO_LOGGEDIN	A set of rules for the seats flow when the user is logged in. The seats MTO flow includes the (Undefined variable: MyVariables.Seatspage) only.

The airline can control the travellers use any of the servicing options based on the rules specified. The rules are defined in STAN and they can be defined either as inclusion or exclusion of items.

The airline may choose to configure a different set of rules for each of the booking flows within the MYB booking flow, and also depending on whether the user is logged in or not. For example, a different set of rules can be defined for changing the itinerary than for cancelling or refunding it.

MYB Rules

It is not necessary to use all the rules available; only use those which are applicable to the airlines business. The following approach may be helpful for developing a set of rules:

1) Determine which rules are needed based on business practices:

For example, if the airline does not allow exchanges for multi-city bookings, use the MultiCityRule to disallow them. if the airline has no policy for exchanging multi-city bookings, you don't need to use this rule.

2) Some rules have parameter values.

For example, if an airline has a time limit for exchanges after the initial booking, you can implement this with the HoursFromBookingRule by including the time limit as a rule parameter.

3) For each rule you use, determine whether it is more effectively implemented as an allow or disallow rule.

If the airline allows exchanges for most booking classes and only disallows a few booking classes, you can implement this with the BookingClassRule. In this case it will be more efficient as a disallow rule that specifies the few classes that customers are not allowed to exchange.

4) Some rules need multiple occurences to describe them completely.

If you are setting up the BookingClassRule to disallow several booking classes, the developer will set up several copies, with each copy disallowing one booking class.

5) Determine the optimum order of the rules you are using. Generally, rules that exclude a large number of potential requests should come near the beginning of the rule set.

If refunds are not allowed for users who are not logged in, you want to put that rule at the beginning of the rule set, because it will immediately reject any user who is not logged in and prevent any further testing of the user's request.

The IBE is filtering for the requests you want to disallow; even when a rule is used to specify what is allowed, the rules engine will detect what is disallowed and trigger a message to the end-user.

MYB Rules list

The following table lists the rules that are available to you. The rules are listed in alphabetical order, but as mentioned above, IBE applies the rules in the order in which they occur in the table and you want to use them into most efficient order.

Criterion	Description	Parameter format	Sample expression
alwaysFalse	This rule always returns false.		alwaysFalse
Ancillaries	Allows or disallows requests based on whether the original booking includes any ancillaries. If any segment of the booking includes any ancillary, the rule is applied.	N/A	allow or disallow
BookingClass	Allows or disallows requests based on the booking class of the original booking. If any segment of the original booking includes the specified booking class, this rule is applied. To allow or disallow multiple booking classes, the developer can create multiple copies of this rule, each specifying a different booking class.	booking class code	allow (bookingClass) or disallow (bookingClass)
CarBookingForMorAirline	Disallows canceling or exchanging PNRs with a car segment when the airline is the Merchant of Record.	CarBookingForMorAirline	Disallows canceling or exchanging PNRs with a car segment when the airline is the Merchant of Record.
CabinId	Allows or disallows requests based on the cabin ID of the original booking. If any segment of the original booking includes the specified cabin ID, this rule is applied. To allow or disallow multiple cabin IDs, the developer can create multiple copies of this rule, each specifying a different cabin ID.	CabinId	Allows or disallows requests based on the cabin ID of the original booking. If any segment of the original booking includes the specified cabin ID, this rule is applied. To allow or disallow multiple cabin IDs, the developer can create multiple copies of this rule, each specifying a different cabin ID.
CodeshareFlight	Allows or disallows PNRs that contain codeshare flights.	CodeshareFlight	Allows or disallows PNRs that contain codeshare flights.
EndorsementNonref	Allows or disallows requests when the original booking contains a text string that identifies the booking as non-refundable. The text string to be matched depends on the wording that the airline uses to identify non-refundable tickets. If the airline uses more than one such text string, the developer can create multiple copies of this rule, each matching a different text string.	EndorsementNonref	Allows or disallows requests when the original booking contains a text string that identifies the booking as non-refundable. The text string to be matched depends on the wording that the airline uses to identify non-refundable tickets. If the airline uses more than one such text string, the developer can create multiple copies of this rule, each matching a different text string.
ExchangedTicket	Allows or disallows requests when the original booking includes a ticket that has already been exchanged. Applies if any passenger in the booking has a ticket that was previously exchanged.	ExchangedTicket	Allows or disallows requests when the original booking includes a ticket that has already been exchanged. Applies if any passenger in the booking has a ticket that was previously exchanged.
HasETicket	Allows or disallows requests when the original booking includes any e-ticket that has already been issued. If any passenger in the booking has an e-ticket, this rule applies	HasETicket	Allows or disallows requests when the original booking includes any e-ticket that has already been issued. If any passenger in the booking has an e-ticket, this rule applies
UnknownTicket	Allows or disallows requests when the original booking includes tickets with unknown status. Applies when all e-ticket coupons in the original booking have an unknown status	UnknownTicket	Allows or disallows requests when the original booking includes tickets with unknown status. Applies when all e-ticket coupons in the original booking have an unknown status
UsedTicket	Allows or disallows requests when the original booking includes e-tickets that have been used. For the purposes of this rule, an e-ticket is considered used when all of its coupons have been used.	UsedTicket	Allows or disallows requests when the original booking includes e-tickets that have been used. For the purposes of this rule, an e-ticket is considered used when all of its coupons have been used.
FareBasis	Allows or disallows requests based on the fare basis of the original booking. If the fare basis for any segment of the original booking includes the specified fare basis, this rule is applied. To allow or disallow multiple fare bases, the developer can create multiple copies of this rule, each specifying a different fare basis.	FareBasis	Allows or disallows requests based on the fare basis of the original booking. If the fare basis for any segment of the original booking includes the specified fare basis, this rule is applied. To allow or disallow multiple fare bases, the developer can create multiple copies of this rule, each specifying a different fare basis.
FormOfPayment	Allows or disallows requests based on the FOP of the original booking. If the FOP for any segment of the booking includes the specified FOP, this rule applies. To allow or disallow multiple FOPs, the developer can create multiple copies for this rule, each specifying a different FOP.	FormOfPayment	Allows or disallows requests based on the FOP of the original booking. If the FOP for any segment of the booking includes the specified FOP, this rule applies. To allow or disallow multiple FOPs, the developer can create multiple copies for this rule, each specifying a different FOP.
HoursFromBooking	Allows or disallows requests based on the time that elapsed since the original booking.	The number of hours as an integer value	HoursFromBooking
Interline	Allows or disallows requests when the original booking is an interline booking. Applies to all itineraries that include an interline booking.	N/A	Interline
ItineraryType	Allows or disallows requests based on whether the itinerary is international. If either tie origin or destination is different from the specified home country, the flight is considered international and this rule is applied.	ItineraryType	Allows or disallows requests based on whether the itinerary is international. If either tie origin or destination is different from the specified home country, the flight is considered international and this rule is applied.
Destination	Allows or disallows requests based on the destination of the original booking. If the destination endpoint for any segment of the original booking includes the specified destination, this rule applies. To allow or disallow multiple destinations, the developer can create multiple copies of this rule, each specifying a different destination.	Destination	Allows or disallows requests based on the destination of the original booking. If the destination endpoint for any segment of the original booking includes the specified destination, this rule applies. To allow or disallow multiple destinations, the developer can create multiple copies of this rule, each specifying a different destination.