Skip to end of metadata
Go to start of metadata

On this page, additional fields can be defined, which will appear on the profiles depending on the selected type of profile.

The following sections (General, Preferences, Your (Agency name) team, Travel documents and Administration) have already been programmed and can be selected from the drop-down list so that the newly created custom fields appear under these sections of either the traveller or company profile. In addition, new sections can be defined using a unique "section name" by choosing "custom" from the drop-down list and then entering the desired name under the various language preferences. Should it be necessary that the section name differs based on the language of the users, then the translation has to be given in in the respective field (see attached example).




  • Inside the section the position of the relevant field can be rearranged by using the drag & drop functionality (click and hold then drag and drop in the desired position)
  • New fields can be added just by clicking on "new custom field" in the field definition section.
  • At the bottom of the field definitions section, a new section can be added by clicking on "new section"


The number of interfaces visible under custom field definitions is a reflection of the interfaces that have been activated on a particular agency. We therefore will cover all the possible interfaces in description below.




This is the title of the determined field. This will be displayed to the end user

Type of ProfileSelect from Traveller or Company. This decides which profile the field will display. If the "-" is selected it will show on both profiles

The following obligations can be selected: Optional, Mandatory, Company-specific

  • Optional - This is to be chosen if it is not compulsory to fill the field
  • Mandatory - This is selected if the field must always be filled
  • Company-specific - This is only visible on the agency setup. This can be assigned if a particular field should only be utilized on traveller profiles of only some but not all companies

Publishing verbiage

<internal code>

Is automatically created with the same value of the field “Label”. It can only be overwritten at time of creation. Existing name values cannot be modified. The value of the Name field can be used for any COPY action in the custom publish action, and is reflected in the CSV file as a designation of the field. To use the Name within a COPY action genInternal has to be included to the name for the source, i.e. genInternalAdditionalEmail

The generic field validation rule can be specified. The format is basically a "regular expression". Some typical examples are:

.{5,7}Any characters, but length min 5 characters max 7 characters
[a-zA-Z]{3,}Only letters, length min 3 characters

In addition, a list of possible values can be defined. For this purpose a semicolon-separated list is entered, with leading string'[L'. Examples

  • [L;Compact;Limousine;Sedan
  • [L=-;CMP=Compact;LIM=Limousine;SED=Sedan

The first example is written as a field value 'Sedan', the second 'SED'

Read/Write (visibility)

  • Agency only: the field is visible and editable only for Travel Agency Admins
  • Read only: the field is always visible to Travel Agency Admins, Company Admins as well as travellers but only editable for the Agency Admins
  • Read & Write: the field is always visible and editable for all users
  • Company only: the field is visible and editable only for Travel Agency Admins and Company Admins
Input typeSelect type of box to display. Possible values are INPUT (regular, single-line text field) and TEXTAREA (multiline text field)
Area to placeWhere in the profile should this new field be positioned
InternalThis field is visible to System-Admins (Support) only and only used on some agency setups. The internal code can also be used for a copy in the custom publish action to transfer generic field values from the company into a GDS traveller profile. The source must be entered with "company.geninternal<internalcode>" e.g company.geninternalmailgmt

Target of where you would like to publish if not using "custom publish actions"

This is where you will add publishing actions if they are mapped directly to a place in the selected interface

Click the left to expand your selection to add the specific publish action to the interface (right) or to update the language (left) of manually built custom fields

CSX PrefixHere the Amadeus prefix is entered. Possible prefixes AB, AM, AP, APE, ES, FD, FK, FT, FZ, OP, OS, PHI/G-, PCI/G-, PCO, PN, PLS, PPR, PPS, PPT, SR, ST, RM, RC, RX, RMC (Category Remarks), RIR).


  • OS prefix: a space is needed by using a airline code and free text (e.g. OS EK BRWD)
  • SR prefix: the SR prefix has to be followed by the identifier, Airline (e.g. SRFOIDLH/)

To include the profile transfer indicator in the prefix, please use:

  • A|(active)
  • S|(selective)
  • M|(mandatory)

in front of the prefix, e.g. A|RM*INFO:{}

Special use of Profile Notes:

Per default all data in the Faces comment field will be published as Amadeus Profile Notes, except if a setup with PN is configured in the custom published action


  • 1|PN = will publish the configured source into line number 1 in the Profile Notes
  • 5|PN = will publish the configured source into line number 5 in the Profile Notes
  • Source: “comment” & Target: “20|PN” = will publish the complete input a the comment field started from Profile Notes line 20.


  • Blank Profile Notes Lines will be filled with a dot (.). Example a copy setup for Profile Line 1 and 3 is configured, in this case line number 2 will be filled with a dot
  • Copy actions other than the source “comment” will be truncated by 56 characters.
GWSHere the Galileo prefix is entered. To include the line number and transfer code (R, N, O, Y) please use
  • 10|Y| = Line number 10 with transfer code Y
  • 23| = line number 23 with Galileo Default transfer code
  • O| = transfer code "O"
  • 6|YH| = Line number 6 with transfer code Y and qualifier H

Example: 10|Y|NP.HX*{}

  • The index of Cytric Free Data Fields
  • The index of Cytric first and second additional Email in the traveller profile
    • firstAdditionalEMail
    • secondAdditionalEMail

Cytric: Process on Free Data File incl. pnrValue

The flag "P|" in the Cytric source is identify the fields will process on FDF incl. “pnrValue”. If the flag has been set and an incoming-cytric.xml contains a FDF incl. “value” and “pnrValue”, Faces will automatically create a validation rule (Regex) with a list of “value” and “pnrValue”

Validation ruleExample
[L<pnrValue>=<value>[LDL=Driving License;NI=DNI;FFIB=Iberia Plus Card;PP=Passport

This list will be also automatically expanded if new values and pnrValues will be delivered in the incoming-cytic.xml. Every prefix on custom fields and custom actions (copy) will only contain the value from “pnrValue”

Flag to identify a FDF incl. “pnrValue”:






This validation will ensure that an empty option is available in Faces, no empty option will be created automatically. If you do not use this validation the list will be expanded automatically i.e. [LHD=Helpdesk;TR=Training;MA=Management. By using the [L=- the list will be created as [L=-;HD=Helpdesk;TR=Training;MA=Management which provides an empty option (-) in the Faces drop down

ConcurA corresponding Concur source is inserted here. These can be found under Concur Sources
EvolviA corresponding Evolvi source is inserted here
Get ThereA Get There source is entered here
SabreA Sabre source is entered here
FarelogixA Farelogixsource is entered here
BillingThe index of Commercial Data
  • No labels