Creating a new automatic message

This topic explains how to create a new automatic message in the Messaging Definitions module.

• Requirements

• E-mail automatic messages: XSL file with e-mail message.

• How

1. Go to the Business Rules tab and choose Messaging Definitions.

2. A new page is displayed. Click Click here to add a New Automatic message.

The New Item page is displayed.

 

3. In the Event field, select the automatic message event:

Field	Description
External system reservations (excl. flight) unconfirmed	The message will be sent each time a booking for all services excluding flight has been created through OP_SET_PAXFILE has a status that is not OK. With e-mail messages, the itinerary is sent as an attachment.
External system flight reservations unconfirmed	The message will be sent each time a flight is created through OP_SET_PAXFILE has a status that is not OK. With e-mail messages, the itinerary is sent as an attachment.
All transactions confirmed	The message will be sent when a transaction is added to a travel file or the status of a transaction changes in a travel file, and the status of all transactions in the travel file is OK. The system does not look at quote, proposal and remark transactions, cancelled transactions and informative flights. With e-mail messages, the itinerary is sent as an attachment
Receipt issued	The message will be sent when a receipt is issued in the travel file. With e-mail messages, the receipt is sent as an attachment
Send documents	The message is sent when a user marks a travel file as completed
Flight schedule change from interfaces	The message is sent when the details of a flight transaction from a GDS are changed

4. In the Language field, select the UI language of the website from which you want the automatic message to be sent.

5. In the Message Content section:

1. For e-mail automatic messages, select E-mail.

2. Click Choose File and upload the custom XSL file with the automatic e-mail message.

3. For text messages, select Text message.

4. Enter the message content.

The content of the message can contain specific strings which are replaced with travel file and transaction data. For example, "Dear {First name} {Last name} becomes "Dear Allan Banks."

5. In addition to the full airline name, the message can also contain the airline's IATA code. This way you can configure messages that include only the name, only the IATA code or both fields. To include the airline's IATA code in the message, use the following reserved key word: {AirlineCode_new}. To include the previous airline IATA code, use: {AirlineCode_old}.

Click here for a full list of strings that can be replaced with travel file data The strings are case sensitive. The following strings can be used in the message. String Description {TravelFileNumber} The travel file number {CustomerTitle} The customer title {CustomerFirstName} The customer's first name {CustomerLastName} The customer's last name {Destination} The travel file destination {TravelFileStartDate} The travel file start date {TravelFileEndDate} The travel file end date {ReservationNumber} The reservation number {Acknowledge} An e-mail acknowledgement link {CompanyInformation} The company name defined in the General Details module The following strings can only be used with  External system reservations unconfirmed messages. {OutboundDepartureDate} The outbound flight departure date {OutboundDepartureTime} The outbound flight departure time {OutboundArrivalDate} The outbound flight arrival date {InboundDepartureDate} The inbound flight departure date {OutboundFrom} The outbound flight departure airport {InboundFrom} The inbound flight departure airport {OutboundAirline} The outbound flight's airline {InboundAirline} The inbound flight's airline {OutboundFlightNumber} The outbound flight number {InboundFlightNumber} The inbound flight number {OutboundTo} The To field in the outbound transaction. If there are multiple legs, the final destination. {OutboundArrivalTime} The outbound flight arrival time (final destination) {InboundDepartureTime} The inbound flight departure time {InboundTo} The To field in the inbound transaction. If there are multiple legs, the final destination {InboundArrivalDate} The inbound flight arrival date (final destination) {InboundArrivalTime} The inbound flight arrival time (final destination) The following strings are used in messages created for messages sent after flight reservations are changed in the Change Flight Reservations module. {Origin_New} The origin of the new flight leg {Destination_New} The destination of the new flight leg {DepartureDate_New} The departure date of the new flight leg {DepartureTime_New} The departure time of the new flight leg {ArrivalDate_New} The arrival date of the new flight leg {ArrivalTime_New} The arrival time of the new flight leg {Airline_New} The airline name of the new flight leg {AirlineCode_New} The airline IATA code of the new flight leg {Origin_Old} The origin of the old flight leg {Destination_Old} The destination of the old flight leg {DepartureDate_Old} The departure date of the old flight leg {DepartureTime_Old} The departure time of the old flight leg {ArrivalDate_Old} The arrival date of the old flight leg {ArrivalTime_Old} The arrival time of the old flight leg {Airline_Old} The airline name of the old flight leg {AirlineCode_Old} The airline IATA code of the old flight leg The following strings can only be used with  Receipt issued messages. {ReceiptSystemAmount} The receipt amount in the system currency {ReceiptFormOfPayment} The form of payment for which the receipt was issued {ReceiptCurrency} The receipt currency

6. Click Save.

Related links

• Business Rules - Messaging Definitions