The Rules Engine allows Airlines to customize many aspects of the services they are using. Rules Engine pinned to services (as per Configuration) sets up special behaviors of the system, e.g.:
- not offering a particular FOP (Form of Payment) fop X minutes before departure
- not offering a particular FOP on some flow
- changing passenger validation based on O&D (Origin & Destination)
- configuring available FOPs per currency of payment
- controlling the specific FOPs available to a Point of Sale
A set of rules can be executed before and/or after each call to a Digital Connect service.
Configuration mutation with rules engine (B2C & MYB): Possibility to attach rule to service in the particular flow – for example to offer PayPal payment in B2C but not in MYB: CI.
By using the rules engine an Airline can set up below example scenarios (to Manage Form of Payment FOP Availability):
- not offering a particular FOP (Form of Payment) for international flight
- not offering a particular FOP for a particular origin country
- not offering a particular FOP for a particular origin airport
- not offering a particular FOP for a particular destination country
- not offering a particular FOP for a particular destination airport
There are two types of rules which can be defined:
- Mutation Rules
- MYB Rules
Mutation rules is a rules engine that makes it possible to define certain criteria that affect the Digital Connect behavior. Unlike MYB Rules, the Mutation Rules can be used for every Digital Connect service.
You can specify the following criteria, or rules, which Digital Connect will use to evaluate whether a servicing option or mutation to an offering should occur.
You can also use negations of the expressions by adding not in front of the expression. For example, if you want the rule to be applied to bookings that do not have Sydney as the origin, specify
Attaching Rules to JSON Service
The rules are added in SAT and for many cases that requires the activations team assistance. Please contact your Delivery Manager for rules set up.
- Rule can be attached to particular JSON service. Particular JSON service is defined by PATH (example: /air/search) and HTTP METHOD (GET, POST, etc.).
- Rule can be executed BEFORE processing a request and AFTER returning a response.
Each rule has the following properties that you must specify for it:
- Name - enter the rule name using the ruleName format. Do not use spaces.
- Mutation - specifies the service behavior if the criteria defined for a rule are met and the rule is applied. Use the following format:
- Expression - specifies the criteria that must be fulfilled for the rule to be applied.
You can define additional configuration rules for the Manage Your Booking (MYB) flow servicing options using MYB Rule Sets. The supported servicing options are:
- changing passenger details
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 Digital Connect 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 are applied.
A key concept is the rules set. If you look at the names of the rules sets - e.g.
EXCHANGE_GUEST, CANCEL_GUEST, EXCHANGE_LOGGEDIN, you will see that they represent categories of services requested (cancel, exchange, upgrade, or update details) and passenger's status (guest or logged in user). Requests for services are matched to rule sets - e.g. 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's statuses.
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 first rule that results in failure in evaluation.