My agency: Unterschied zwischen den Versionen
(→System Settings) |
(→System Settings) |
||
| Zeile 86: | Zeile 86: | ||
| Rail | | Rail | ||
| | | | ||
| − | * - = no | + | * - = no Rail |
* AMADEUS_GERMAN = Railprovider DB (Deutsche Bahn), SBB (Swiss Railway) | * AMADEUS_GERMAN = Railprovider DB (Deutsche Bahn), SBB (Swiss Railway) | ||
* AMADEUS_RAIL = Railprovider DB (Deutsche Bahn), SNCF, Thalys, Swedish Railways | * AMADEUS_RAIL = Railprovider DB (Deutsche Bahn), SNCF, Thalys, Swedish Railways | ||
different Formats are used in Amadeus CSX for AMADEUS_GERMAN and AMADEUS-RAIL (see Mapping) | different Formats are used in Amadeus CSX for AMADEUS_GERMAN and AMADEUS-RAIL (see Mapping) | ||
|- | |- | ||
| + | | Railmaster PCC | ||
| + | | used Galileo Railmaster PCC | ||
| + | |- | ||
| + | | Browser-Extension | ||
| + | | activates the useage of Browser Extension | ||
| + | |- | ||
| + | | Profile Reminder | ||
| + | | activates the useage of Profile Reminders | ||
| + | |- | ||
| + | | Loyalty Points | ||
| + | | no in use, will be decommissoned | ||
| + | |- | ||
| + | | Residence Information | ||
| + | | activates the useage of Residence Information for the Spanish market | ||
| + | |- | ||
| + | | No. of companies | ||
| + | | Shows the total numbers of Company profiles in the agency | ||
| + | |- | ||
| + | | No. of travellers | ||
| + | | Shows the total numbers of traveller profiles in the agency | ||
|} | |} | ||
Version vom 13. März 2017, 08:50 Uhr
Inhaltsverzeichnis
Overview
In this tab the travel agency is managed (depening on access authorization)
Layout
User Interface
Section 'Address'
All information entered here will appear by clicking on the tab "My travel agency,". This information is also displayed at the top right of the blue bar.
| Field | Description |
|---|---|
| Name | Name of Travel Agency |
| Street | Street of Travel Agency |
| PLZ | Postal code |
| Location | Location of Travel Agency |
| Country | Country where Travel Agency is located |
| Phone | Insert phone number of Travel Agency |
| URL | Insert the URL of the Travel Agency |
| Send profile updates to | This field indicates to which Email account an alert about an update or change will be sent. Emails would only be triggered if changes are executed by travellers or company admins.
If changes are done by the agency admin no email alert is send. In case of no email address is inserted, no alert emails will be sent. (Email Alert example below) |
| Send system notifications to | A system notification is an email message which informs about incoming AeTM or Cytric update/creation profiles, which cannot be processed due to technical reason, e. g. Cytric Org Id or AeTM Community not existing in Faces, User login is already in use etc. An email address can be entered to which the notification should be sent. |
Email Alert example:
Section 'Privacy policy'
In this section, additional Privacy policy can be created and the user can be forced to re-accept the privacy policy condition within the next login. Privacy policy can be created in all different available language preferences.
The klick on "Add new" will display a Editor in which new conditions can be created.
Important:The privacy policy will be shown after the general Umbrella Faces policy.
System Settings
| Field | Description |
|---|---|
| Acitve | deactive or active agency |
| Key | Agency Key |
| Faces | activates the usage of Faces |
| Self-booking | activates the useage of SBT (not deployed) |
| Accelerators | activates the useage of Robotic Tools |
| PCI DSS | acitvates the useage of PCI DSS Module |
| Rail |
different Formats are used in Amadeus CSX for AMADEUS_GERMAN and AMADEUS-RAIL (see Mapping) |
| Railmaster PCC | used Galileo Railmaster PCC |
| Browser-Extension | activates the useage of Browser Extension |
| Profile Reminder | activates the useage of Profile Reminders |
| Loyalty Points | no in use, will be decommissoned |
| Residence Information | activates the useage of Residence Information for the Spanish market |
| No. of companies | Shows the total numbers of Company profiles in the agency |
| No. of travellers | Shows the total numbers of traveller profiles in the agency |
Section 'CSX Webservice'
| Field | Description |
|---|---|
| WS App | Abot or Faces |
| User ID | Amadeus User ID |
| Password | Password |
| Accesspoint | Amadeus WSAP |
| Office ID | Insert Office ID |
| Org. ID | Insert the ID of the organization
By clicking on <Test Login> the connection to Amadeus can be tested |
| Publish passport | The Passport data
|
| Publish mobile-no. | The mobile number
|
Section 'AeTM'
| Field | Description |
|---|---|
| User name | Interface name to Amadeus Profile Link |
| Password | Password
By clicking on <test login> the connection to AeTM Profile Link can be tested |
Section 'Galileo WS'
| Field | Description |
|---|---|
| User name | Galileo PCC e.g. PCC7E1N |
| Host Access Profile | Galileo HAP e.g. DynGalileoProd_7E1N |
| PCC | Galileo Pseudo City Code. e.g. 7E1N |
| Password | Password
By clicking on <test login> the connection to Galileo can be tested |
| Use Travelscreen | Activation of Travelscreen useage |
Section 'Cytric'
| Field | Description |
|---|---|
| Client ID | Client ID name of Cytirc |
| Username | Cytric system |
| Password | Password
By clicking on <test login> the connection to Cytric can be tested |
Section 'umbrella.net'
| Field | Description |
|---|---|
| Client ID | umbrella.net Client ID (Mandanten ID) |
| URL | relevant target URL for umbrella.net |
Setup and configuration for umbrella.net can be found in the online documentation .
Section 'Custom Field definitions'
On this page, additional fields can be defined, which will appear on the profiles depending on the selected type of profile. General, preferences, your team, travel documents and administration can be selected. In addition, new sections can be defined with a unique label. This selection determines, in which sections the defined field appear on the profiles.
Tipp: Inside the section the position of the relevant field can be rearranged by using the drag & drop functionality
| Field | Description | ||||||
|---|---|---|---|---|---|---|---|
| Label | This is the title of the determined field | ||||||
| Mandate | The following obligations can be selected: O = optional, M = mandatory, CS = company-specific. | ||||||
| R/W ( visibilitiy) |
| ||||||
| CSX Prefix | Here the Amadeus prefix is entered. Possible prefixes AB, AM, AP, APE, ES, FD, FK, FT, FZ, OP, OS, PHI/G-, PCI/G-, PCO, PN, PPR, PPS, SR, RM, RC, RX, RMC (Categorie Remarks), RIR).
Specific's:
To include the profile transfer indicator in the prefix, please use:
infront of the prefix, e.g. A|RM*INFO:{} Special use of Profile Notes: Per default all data in the Faces comment filed will be published as Amadeus Profile Notes, except 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*{} | ||||||
| AeTM | The index of AeTM Custom Fields and traveller profile fields Email2 and Email3 | ||||||
| Cytric |
| ||||||
| Billing | The index of umbrella.net Commercial Data | ||||||
| Name | 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 filed can be used for any COPY action in the custom publish action, and is reflected in the CSV file as designation of the field. To use the Name within a COPY action genInternal has to be included to the name for the source, e.g. genInternalAdditionalEmail. | ||||||
| Internal | System-Admin (Support) ony. The internal code can also be used for a copy in the custom pubish action, to transfer generic filed values from the company into a GDS traveller profile. The source must be enter with "comany.geninternal<internalcode>" e.g company.geninternalmailgmt. | ||||||
| Field | Possible values are INPUT (regular, single-line text field) and TEXTAREA (multiline text field) | ||||||
| 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' | ||||||
| Profile Type | A distinction is made between Traveller and Company, T (Traveller) and C (Company) for the profile type on which the profile box appears |
Section 'Custom Publish Actions'
| Field | Description |
|---|---|
| Action | Select COPY or FILTER for your action |
| Type of Profile | A distinction is made between Traveller and Company, T (Traveller) and C (Company). Select the Type of Profile on which the profile box appears. |
| Source | Indicate the source respectively the corresponding filter. |
| Target | Indicate the target or insert a free text if using the filter function. |
The source for the COPY function company data profile can be found under Company The source for the COPY function Traveller data is visible at line 1 in the CSV file. If 0-n lists (FQTV or passports) are copied, either an index (passports0, passports1) can be used, or use the index placeholder '#' (# passports). The latter then copies all existing indexes.
FILTER examples can be found under profile Traveller | and profile Company
Import/export generic setup
(available with the next release, planed 18th October 15)
A export and/or import from the agency generic setup of custom field definitions and custom publish actions in a XML schema file. The XML file can be used for a upload to a existing agency.
Workflows / Processes
New fields can be added just by clicking on "Add New" in the field definition section. At the bottom of the field definitons section, a new section can be added by clicking on "Add New".
The publish actions can be added by clicking on "Add New".
