R19 release notes
These release notes describe the features and fixed issues included in R19. To determine the release installed in your org, see Installed Packages.
To learn how to enable the R19 features, see the R19 feature enablement guide.
For assistance with any feature configuration, please contact your Amadeus sales representative to learn more about our Professional Services offerings.
New features and enhancements
Instructions for enabling the R19 features can be found in the following topics:
- Add alternate language fields to page layouts
- Assign alternate language permission sets to users
- Update merge templates for alternate languages
Support for alternate languages
If you regularly book business with international customers, being able to communicate in multiple languages is crucial to executing flawless events and ensuring your customer’s satisfaction. With R19, you have the tool set you need to translate key booking and event information in different languages. Now you can create BEOs, banquet checks, and Advanced Booking merge documents in one or two languages using the translations your team has provided in the new alternate language fields.
R19 includes support for the following languages: English (US), German, Spanish, French, Italian, Dutch (NL), Polish, Portuguese (Brazil), Portuguese (Portugal), Chinese (Simplified), and Chinese (Traditional). A Corporate Administrator provides users with access to one or more alternate languages using permission sets. You’ll only see the alternate language fields for those permission sets that have been assigned to you.
Alternate language fields
Alternate language fields are included for several page layouts. If you’re upgrading to R19, a Corporate Administrator will need to add the alternate language fields to the corresponding page layouts for each language that is supported at your property. If you’re a new installation, these fields will automatically appear on your page layouts.
Once translations have been entered in these fields, they can be displayed on BEOs, banquet checks, and Advanced Booking merge documents. The translations that are provided for menus and items are also displayed in the Editing Item Details window and can be used as search criteria in the Menu and Item Search window.
Here are each of the page layouts that support multi-language and the alternate language fields that can be added to each one. In some cases, multiple page layouts need to be configured for an object (see bullets).
| Pages | Alternate language fields |
|---|---|
| Booking Other Income | Name Abbreviation Description |
| Booking Package | Display Name Abbreviation Description |
Booking Terms and Conditions
|
Name Terms |
Event Classification
|
Name Abbreviation Description |
Event Item
|
Name Rich Description Sold By Units |
Function Room
|
Function Room Name Abbreviation |
| Guestroom Type | Name Room Type Code If your property is integrated with a PMS, do not translate Room Type Code. |
Item
|
Name Rich Description Sold By Units |
| Other Income | Name Abbreviation Description |
| Package | Name Display Name Abbreviation Description |
Property
|
Property |
Setup Value
|
Value Abbreviation |
| Terms and Conditions | Name Terms |
Alternate language permission sets
Permission sets determine which languages you can see. A Corporate Administrator assigns each user the appropriate permission sets using the Permission Set Assignments related list on the User page.
For example, if you’ve been assigned a single permission set for French, you’ll only see the French alternate language fields—even if German and Italian fields have also been added to the page layout. Your alternate language permission sets are applicable at any property you have access to. They also determine which languages you can choose to display in merge documents.
View and modify alternate language fields
An administrator can populate the alternate language fields in each area of Setup (menus and items, event classifications, function rooms, etc.). You’ll be able to see the translations when you’re working as long as you have the corresponding permission sets.
When you’re detailing a BEO, you can confirm that all the menus and items have been translated correctly by clicking the new Edit Translations button on the Editing Item Details page. This opens a window where you can see all the translations for the alternate language permission sets that have been assigned to you. If a translation needs to be entered or modified, you can do so directly in the Edit Translations window. Your changes will not overwrite the master translations entered in Setup.
Another new feature is found on the Manage Menus and Items page. Now you can search for menus and items using an alternate language. For example, if you’ve been assigned the French alternate language permission set, searching on “saumon” will return the Roasted Salmon menu (saumon rôti).
Merge with alternate language fields
R19 allows you to create BEOs, banquet checks, and Advanced Booking documents in one or two languages. This functionality is available whether you’re merging a single document or batch merging multiple documents.
If you’re creating merge documents using any single language, your merge templates will work as is. No additional configuration of your merge tags is required. You may, however, want to create a unique merge template for each language and then translate the text and field labels into the appropriate language.
If you’d like to create bilingual merge documents (for example, your default language and French or German and French), you’ll need to add the secondary merge fields to your merge templates. These fields are available in the Amadeus Merge Add-In Tool version 3.6.9.4 or higher. Because they are dynamic, they only need to be added to each template once and will automatically update for each language that is selected for the merge. Just as with single language documents, you may also want to create a unique template for each language combination and then translate the text and field labels into the appropriate languages.
Currently, not all alternate language fields can be added to Advanced Booking merge documents. Don’t worry. We’re already making sure more of these fields will be available in upcoming releases.
Here are a few additional things to keep in mind:
- Only those languages that you have been given access to through permissions sets will be available for selection in the Language and Secondary Language picklists when you’re merging and batch merging.
- You must select a BEO, Banquet Check, or Advanced Booking template to display the Language and Secondary Language picklists on the merge pages.
- If you don't have any alternate language permission sets, you won't see the Language and Secondary Language picklists on the merge pages.
- If you select a language that does not have translations entered, we will use your default language (for example, English) where the alternate language fields are blank. For example, if your item name has been translated into French but its description has not, the merged BEO will show the French name and the English description.
Fixed issues
Availability
CR0122576: The Custom Status field on the Booking page can now be viewed in the Guestroom Bookings section of the Availability 2.0 page.
Bookings
CR0122137: The administrative charge on function room rental now rolls up into the Admin Revenue section on a booking and event.
Inquiries
CR0091333: You can now create a booking from an RFP inquiry when a matching account is not found in the system. We will create the new account and contact accordingly.
Merge
CR0122572: Clicking Go to Merge in the Preview & Merge window (Manage Events page > BEO > Preview & Merge) no longer displays an error message when the events on a cross-property booking use different property-level BEO templates.