Creating a new manual message

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

• How

1. Go to Setup – Business Rules – Messaging Definitions.

   

2. Select the Manual Messages tab.



3. Click Click here to add a new Manual message.

The New Item page is displayed.



4. In the Message name field, enter the name of the manual message.

5. In the Language field, select the language of the message you want to send.

6. In the Message Content section:

1. For e-mail 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."

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

7. Click Save.

Related links

• Business Rules - Messaging Definitions