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).
Tips:
- 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"
Overview
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.
Description
| Field | Description | ||||||
|---|---|---|---|---|---|---|---|
| Label | This is the title of the determined field. This will be displayed to the end user | ||||||
| Type of Profile | Select from Traveller or Company. This decides which profile the field will display. If the "-" is selected it will show on both profiles | ||||||
| Optional/Mandatory | The following obligations can be selected: Optional, Mandatory, Company-specific
| ||||||
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 | ||||||
| Validation | The generic field validation rule can be specified. The format is basically a "regular expression". Some typical examples are:
In addition, a list of possible values can be defined. For this purpose a semicolon-separated list is entered, with leading string'[L'. Examples
The first example is written as a field value 'Sedan', the second 'SED' | ||||||
Read/Write (visibility) |
| ||||||
| Input type | Select type of box to display. Possible values are INPUT (regular, single-line text field) and TEXTAREA (multiline text field) | ||||||
| Area to place | Where in the profile should this new field be positioned | ||||||
| Internal | This 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
| |||||||
| CSX Prefix | Here the Amadeus prefix is entered. Possible prefixes AB, AM, AP, APE, ES, FD, FK, FT, FZ, OP, OS,PFO (Follow up entry), PHI/G-, PCE, PCI/G-, PCO, PN, PLS, PPR, PPS, PPT, SR, ST, RM, RC, RX, RMC (Category Remarks),RII, RIR). Specific's:
To include the profile transfer indicator in the prefix, please use:
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 Targets:
Rules/General:
| ||||||
| GWS | Here the Galileo prefix is entered. To include the line number and transfer code (R, N, O, Y) please use
Example: 10|Y|NP.HX*{} | ||||||
| Cytric |
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”
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”: P|<FDF-Name> Example: P|Costcenter Validation: [L=- 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 | ||||||
| Concur | A corresponding Concur source is inserted here. These can be found under Concur Sources | ||||||
| Evolvi | A corresponding Evolvi source is inserted here | ||||||
| Get There | A Get There source is entered here | ||||||
| Sabre | A Sabre source is entered here | ||||||
| Farelogix | A Farelogixsource is entered here | ||||||
| Billing | The index of umbrella.net Commercial Data | ||||||
