Profile Traveller: Unterschied zwischen den Versionen
Zeile 1'265: | Zeile 1'265: | ||
| | ||
+ | |||
===== Cytric Source ===== | ===== Cytric Source ===== | ||
Zeile 1'347: | Zeile 1'348: | ||
home_mobile | home_mobile | ||
+ | |||
+ | Home Email | ||
+ | |||
+ | home_email | ||
My Air Travel Preferences - Default Departure City | My Air Travel Preferences - Default Departure City |
Version vom 15. Dezember 2017, 10:34 Uhr
Inhaltsverzeichnis
Overview
In this tab traveller profiles are managed.
Layout
User Interface
For User authorization levels and other features click here Administrator
Section 'Login'
In the 'Login' section, the login details for Umbrella Faces are managed.
Field | Description |
---|---|
User name | Any user name can be chosen, but must be unique within a travel agency. |
Password | The password must contain at least 8 characters and contain at least one letter and one number.
If the traveller has no password, a password will be proposed. |
Send access | Here, the access to the traveler or to the associated travel arranger can be sent. |
Section 'Publishing'
Field | Description |
---|---|
Amadeus CSX, Profile number | The result of the last transmission to CSX appears, together with the record locator of the profile. |
Galileo WS, Profile number | The result of the last transmission to GWS appears, together with the PAR Title of the profile. |
AeTM, User name | The result of the last transmission to AeTM appears, together with the AeTM Login name. |
Password, Confirm Password | Enter AeTM Passwort |
Cytric, Profil no | The result of the last transmission to Cytric appears, together with the Cytric Login name. |
Main Travel Group | AeTM Community and Role or Cytric Travel Policy Group and Role
For each AeTM community and Cytirc Org-Id which is defined on the associated Company, the role of the traveller can be defined here. The traveller must have a Home Community mandatory. AeTM Roles:
Cytric Roles:
For Agencies in which both interfaces (AeTM and Cytric) are activated, the Faces-Roles are displayed before the profile is assosiated to the company (first save). For Agencies with only one interfaces the relevant roles are chose able. Faces Roles:
|
Section 'General'
Field | Description |
---|---|
Company | The company, to which the traveller is associated |
Gender | 'Mr', 'Mrs', 'Ms' or 'Unkown' |
Title | As titles are currently available:
|
First name | The first name of the traveller as in the passport. This is a required field. |
Middle name | Here you can specify an optional middle name, according to the passport |
Surname | The last name of the traveller as in the passport. This is a required field |
Date of birth | The date of birth of the traveller. This is a required field for the traveller and company administrators.
For supporters and agency administrators this field is 'no' required field. |
Citizenship | Here the citizenship is registered by choosing the country of origin |
Language | Here the language of the user interface can be selected |
Phone business | Register the business phone number of the traveller |
Phone private | Register the private phone number of the traveller |
Mobile | Register the mobile phone of the traveller |
Register the E-Mail address of the traveller | |
Itinerary / e-ticket | If this checkbox is disabled, a '* PAX' is entered in the CSX profile before the e-mail address to devalue the address (eg PAX*NAME@COMPANY.COM) |
Out of Office until | The absence of the traveller (relevance for approvers) |
Traveller |
If this box is checked, the travellers profile is a traveller. Can only be assigned by the supporter or company administrator / profile manager. |
Arranger / Assistance |
If this box is checked, the travellers profile is an arranger. Can only be assigned by the supporter or company administrator / profile manager. |
Approver |
If this box is checked, the travellers profile is an approver. Can only be assigned by the supporter or company administrator / profile manager. |
Credit cards | If "Personal Credit Cards" are allowed on the Company, the traveller may deposit its private credit cards here. |
Card Type | Credit Card type |
Creditcard no. | Credit Card of the traveller |
Expiration | The expiration date of the credit card |
Use as form of payment | This credit card is written as FoP (F. or FP) in the GDS's. |
Add new | Register unlimited credit cards |
Other forms of payment | Selection of "-" none, invoice or cash |
Declaration profile types "Arranger, Approver"
Various functions and privileges can be assigned by activating the checkmark of arranger, approver and profile manager.
Profile Type | Function/Rights |
---|---|
Arranger | can be selected as arranger in the section Administration
With his access, the Arranger is allowed to manage the associated travellers. He can not delete profiles. Module: AeTMAdditionally the role of "appointed travel arranger" and "principal travel arranger" will be listed
Module: CytricAdditionally the role of "Travel Arranger (restricted)", "Travel Arranger (restricted with Profil Admin)", "Travel Arranger" and "Travel Arranger (all)" will be listed.
|
Approver | can be selected as approver in the section Administration
With his access, the Approver is allowed to manage the associated travellers. He can not delete profiles. Module: AeTMAdditionally the role of "travel approver" and "fallback approver" will be listed.
Module: CytricAdditionally the role of "Trip Approver" will be listed.
|
One or more types can be assigned to a Profile.
Section 'Preferences'
Field | Description |
---|---|
Seat request | Choose between window and aisle seat (the seating preference is taken into account when booking, but it is not guaranteed and subject to change). |
Meal request | Enter food preferences of travellers (eg: Gluten Intolerance). |
Smoker | Check, if the traveller is a smoker. |
Web-card | Select the credit card here, if in the company or traveller profile a web-card is available (web-booking). |
Airline Company program | |
Airline | Enter your airline / alliance frequent flyer program here. |
Number | Register the loyalty program number of the traveller of the airline / alliance here. |
PIN | Register the PIN number of your loyalty program here. |
Hotel Program | |
Hotel guarantee | Select the credit card to guarantee the hotel if available in the company or traveller profile. |
Hotel chain | Enter the Hotel chain here. |
Number | Register the hotel loyalty program number of the traveller here. |
Customer request | Enter specific customer requests manually. |
Car Program | |
Guarantee car rental | Select the credit card to guarantee the car rental if available in the company or traveller profile. |
Rental car company | Select the Rental car company here. |
Number | Register the car loyalty program number of the traveller here. |
Customer request | Enter specific customer requests manually. |
Rail information | |
Card | Select the Card type |
Number | Register the rail loyalty program or/and rail discount number of the traveller. |
Expiration | Enter the expire date of the rail loyalty/discount card. |
Collect points | Activate/deactivate if the traveller wants to collect points |
Class | Preferred Seat Class |
Delivery | Delivery option for the train ticket |
Wagontype | Preferred Wagontype |
Wagon extra | Preferred Wagon extra |
Seat | Preferred Seat for train journey |
Identification | From of Identification to collect train ticket |
Section 'Travel documents'
Field | Description |
---|---|
Passport data | |
Nationality | Enter the nationality of the traveller here. |
Passport number | Enter the passport number here.(all blanks and special characters will be not synchronise to the different interfaces) |
Date of issue | Enter the date of issue of the passport. |
Place of issue | Enter the place of issue of the passport. |
Issue Country | Enter the issue country of the traveller here. |
Expiration date | Enter the date of expiration of the passport. |
Visa Information | |
Country | Register the country for which the visa is valid. |
Number | Enter the visa number here. |
Date of issue | Enter the date of issue here. |
Expiration date | Enter the date of expiration here. |
Entry type | drop down of single, double or multiple entry |
Identification cards | |
Country | Enter the nationality here. |
Number | Register the number of the identification Card. |
Section 'Administration'
The following fields shall apply to the arranger as well as approver and emergency contact
Field | Description |
---|---|
First name | First name of the arranger/approver/emergency contact |
Surname | Surname of the arranger/approver/emergency contact |
E-Mail address of the arranger/approver/emergency contact | |
Phone | Phone number of the arranger/approver/emergency contact |
Itinerary / e-ticket | If this checkbox is disabled, a '* PAX' is entered in the CSX profile before the e-mail address to devalue the address (eg PAX*NAME@COMPANY.COM) |
Section 'Comment'
Any text can be inserted in the 'Comment' field.Comments are published as profiles Notes to the CSX.
Section 'Log'
The log is a history of recent changes. Date, time, user and the status "saved profiles" is displayed
AeTM Integration
If Faces is configured as "profiles exit point" in AeTM, the profile of the traveller will appear in Faces
- The Umbrella Faces Login-Data will be hidden
- The publishing-status will only be shown for AeTM
Workflows / Processes
Create and edit Travellers
Following fields are mandatory in order to create a new profile: User Name, company, gender, first name, surname, email address, birth date
Search travellers
Following terms can be used when searching for a traveller:
- First name
- Last Name
- CSX profile number
- AeTM Username
- Company Name
Send credentials
By clicking on "send credentials" the login information will be sent to the traveller via email. This function always generates a new, temporary password. With the first login, the traveller must set a new password and accept the Privacy Policy.
Technical / Functional Details
Field-Mapping
There is no standard mapping for Galileo. The setup can be individually done in the Custom Publish Actions.
Faces | CSX | AeTM | umbrella.net | cytric |
---|---|---|---|---|
Company | PCN | Company | ||
Username | Login Name | User Name | ||
Main travel group | Community Codes | Travel Policy Group | ||
Add. travel group | Community Codes | |||
Role | Role | |||
Gender | NM (MR / MRS) | Gender | Title | Personal Data/Greeting |
Title | NM | Title of Passenger | Personal Data/Title | |
First name | NM | First name | First name | Personal Data/First name |
Middle name | NM | Middle name | Government ID and Visa Data/Middle name | |
Surname | NM | Surname | Name | Personal Data/Last name |
Date of birth | PBD | Date of birth | Date of birth | Personal Data/Date of birth |
Nationality | PCZ | Personal Data/Country of Citizenship | ||
Language | Preferred Language | Language | Personal Preference/Language Preference | |
Phone business | AP -B | Business Phone | Telephone 1 | Personal Data/Telephone |
Phone private | AP -H | Telephone 2 | Personal Data/Home Address - Telephone (if cytric source for home address is in use, e.g. home_street) | |
Mobile phone | selectively AP -M or APM | Mobile Phone 1 | Mobile | Personal Data/Mobile Telephone |
Depending on the "dispatch e-mail" in the Company Profile:
|
E-Mail 1 | Personal Data/eMail | ||
Form of payment / credit cards | FP (if "use as form of payment is activated) |
|
Credit Cards (Main or Lodge) | Credit Card and Payment Card Information |
Seat request | ST/A oder ST/W | Seat Preference | Booking data-Preferences-Seat | Personal Preference/My Air Travel Preferences/Seat |
Meal request | SR* | Meal Preference | Booking data-Preferences-Food | Personal Preference/My Air Travel Preferences/Special Meal Request |
Smoker | PSH/Y, PSH/N | Smoking Preference | Booking data-Preferences-Smoker | |
Airline Company program | ||||
Airline + Number | FFN
LH card beginning with no. 9999 are published as SR FQTV LH- |
Frequent Flyer |
Booking data-Memberships-Type (Flight) | Frequent Traveller Numbers for Airlines |
PIN | RX | |||
Hotel Program | ||||
Hotel guarantee | PHI/G | Hotel Guarantee/Payment | ||
Hotel chain | PHI/CO | Frequent Hotel Guest/Hotel Chain | Booking data-Memberships-Type (Hotel) | Frequent Traveler Numbers for Hotel Chains |
Number | PHI/ID | Frequent Hotel Guest/Loyalty Number | Booking data-Memberships-Type (Hotel) | Frequent Traveler Numbers for Hotel Chains |
Customer request | PHI/SI | |||
Rental car travel policy | ||||
Guarantee Car Rental | PCI/G | Car Guarantee | ||
Rental car company | PCI/CO | Frequent Renter Membership/Car Renter Chain | Booking data-Memberships-Type (Rentalcar) | Frequent Traveller Numbers for Rental Car Vendors |
Number | PCI/ID | Frequent Renter Membership/Loyalty Number | Booking data-Memberships-Type (Rentalcar) | Frequent Traveller Numbers for Rental Car Vendors |
Customer request | PCI/SI | |||
Rail information</td> | ||||
Card |
Germany Rail:
Amadeus Rail:
|
Rail Discount Card/Card Provider and Type (BC25, BC50, BCB25, BCB50 ) | ||
Number |
Germany Rail:
Amadeus Rail:
|
Rail Discount Card/Card number | ||
Experation |
Germany Rail:
Amadeus Rail:
|
Rail Discount Card/Valid through | ||
Collect points |
Germany Rail:
Amadeus Rail:
|
Frequent Traveler Numbers - Rail/Rail Company and Card Type/Number/Valid through | ||
Class |
Germany Rail:
Amadeus Rail:
|
| ||
Delivery | RM*DB:RW: | |||
Wagontype | RM*DB:RW: | Personal Preferences/My Rail Travel Preferences/Type of Carriage | ||
Wagon extra | RM*DB:RW: | Personal Preferences/My Rail Travel Preferences/Type of Carriage | ||
Seat | RM*DB:RW: | Personal Preferences/My Rail Travel Preferences/Seating preferences | ||
Identification | RM*DB:OLT: | |||
Passport data | Choice between 'PAS' and/or SR DOCS | Passport 1/Passport 2 | Government ID and Visa Data | |
Nationality | PAS/CO | Country of Citizenship | Booking Data-Passport-Nationality | Government ID and Visa Data/Country of Citizenship |
Passport number | PAS/NR | Passport number | Booking Data-Passport-Number | Government ID and Visa Data/Government ID Number |
Issue date | PAS/IS | Booking Data-Passport-Date of issue | ||
Issue Country | Government ID and Visa Data/Issuing Country | |||
Expiration date | PAS/EX | Expiration date | Booking Data-Passport-Expiry Date | Government ID and Visa Data/Government ID Expiry Date: |
Visa Information | ||||
Country | PIV/CO | Government ID and Visa Data/Visa Country | ||
Number | PIV/NR | Government ID and Visa Data/Visa Number | ||
Issue date | PIV/IS | Government ID and Visa Data/Visa Issue Date | ||
Expiration date | PIV/EX | Government ID and Visa Data/Visa Expiration Date | ||
Entry type | Government ID and Visa Data/Visa type | |||
Identification cards | ||||
Country | PID/CO | |||
Number | PID/NR | |||
Arranger | Depending on the "dispatch e-mail" of the Company:
|
Assignement of the arranger (appointed travel arranger / principal travel arranger) | Personal Preferences/Select Travel Arranger | |
Approver | Depending on the "dispatch e-mail" of the Company:
|
Assignement of the approver (travel approver / fallback approver) | Personal Preferences/Select Your Trip Approver for the Basic Approval System | |
Emergency | Depending on the "dispatch e-mail" of the Company:
|
Emergency Contact Name
Emergency Contact Number |
Emergency Contact Information/Name/Telephone | |
Comments | PN |
Profile actions
Amadeus CSX
FILTER
Faces | CSX | FILTER | |
---|---|---|---|
Date of birth | PBD | //generalTravellerInformation/personalTravellerInformation/birthDate | |
Nationality | PCZ | //generalTravellerInformation/personalTravellerInformation/citizenship | |
Phone business | AP -B | //pnrElements[pnrElementInformation/pnrElementIdentification/textSubjectQualifier = '3' and pnrElementInformation/pnrElementIdentification/informationType = '3'] | |
Phone private | AP -H | //pnrElements[pnrElementInformation/pnrElementIdentification/textSubjectQualifier = '3' and pnrElementInformation/pnrElementIdentification/informationType = '4'] | |
Mobile phone |
|
| |
|
|
||
Form of payment / credit cards | FP (if "use as form of payment is activated) | //pnrElements[pnrElementInformation/pnrElementIdentification/textSubjectQualifier='3' and pnrElementInformation/pnrElementIdentification/informationType='16'] | |
Seat request | ST/ | //seatAndServiceRequests[seatAndServiceRequestInformation/seatRequestInformation/seatCharacteristic] | |
Meal request | SR* | //seatAndServiceRequests[substring(seatAndServiceRequestInformation/serviceRequestType/ssrCode, string-length(seatAndServiceRequestInformation/serviceRequestType/ssrCode) - string-length('ML') +1) = 'ML'] | |
Smoker | PSH | //smokingPreferences | |
Airline Company program | |||
Airline + Number | FFN | ||
PIN | RX |
//remarkSection[miscellaneousRemark/miscellaneousRemarkInformation/type = 'RX' and contains(miscellaneousRemark/miscellaneousRemarkInformation/longFreeText, 'PIN')] | |
Hotel Program | //hotelCustomerInformation | ||
Hotel guarantee | PHI/G | ||
Hotel chain | PHI/CO | ||
Number | PHI/ID | ||
Customer request | PHI/SI | ||
Rental car travel policy | //carCustomerInformation | ||
Guarantee Car Rental | PCI/G | ||
Rental car company | PCI/CO | ||
Number | PCI/ID | ||
Customer request | PCI/SI | ||
Rail information | Amadeus Rail Mapping(complete) RMR/PPS |
| |
Travel documents (Documents) | PAS/PIV/PID | //documentSection | |
Arranger Name & Phone | AP <Name> <phone>,/-ARR | //pnrElements[pnrElementInformation/pnrElementIdentification/textSubjectQualifier = '3' and pnrElementInformation/pnrElementIdentification/informationType != 'P02' and contains(pnrElementInformation/longFreeTextData, ',/-ARR')] | |
Arranger | Depending on the "dispatch e-mail" of the Company:
|
| |
Approver Name & Phone | AP <Name> <phone>,/-AUT | //pnrElements[pnrElementInformation/pnrElementIdentification/textSubjectQualifier = '3' and pnrElementInformation/pnrElementIdentification/informationType != 'P02' and contains(pnrElementInformation/longFreeTextData, ',/-AUT')] | |
Approver |
|
| |
Emergency Name & Phone | AP <Name> <phone>,/-ECT | //pnrElements[pnrElementInformation/pnrElementIdentification/textSubjectQualifier = '3' and contains(pnrElementInformation/longFreeTextData, ',/-ECT')] | |
Emergency Email |
|
| |
Comments | PN |
Generell: Filter all email addresses
//pnrElements[pnrElementInformation/pnrElementIdentification/informationType = 'P02' and contains(pnrElementInformation/longFreeTextData, '@')]
COPY
Most sources are also available in the CSV Export file.
Company assignement
company.name
Surname, first name, middle name, gender (GDS Format)
gdsName
Surname, first name, gender (GDS Format)
gdsNameShort
Main Travel Group (Description)
homeCommunityDescription
Visa Information / Entry type
visa#.visaEntry
Last Modification in Profil (Histroy)- used format = DDMMMYY HH:MM
lastModified
Credit Card / only use as Fop = true
fopCreditcards#.
Credit Card / all Credit Cards
sortedCreditcards#.
Car Rental guarantee
carGuaranteeCardExtended
Hotel guarantee
hotelGuaranteeCardExtended
Webcard
webPaymentCardExtended
Credit Card Type
sortedCreditcards#.type
Credit Card Number
sortedCreditcards#.number
Credit Card Expiration
sortedCreditcards#.expiration
Rail Form of Payment
formOfPaymentRail
Other Form of Payment (INV, CAHS)
additionalFormOfPayment
Arranger Contact Email
arrangercontacts#.email
Arranger Contact Firstname
arrangercontacts#.contact.firstname
Arranger Contact Surename
arrangercontacts#.contact.name
Arranger Contact Phone Business
arrangercontacts#.contact.phoneBusiness
Approver Contact Email
approvercontacts#.email
Approver Contact Firstname
approvercontacts#.contact.firstname
Approver Contact Surename
approvercontacts#.contact.name
Approver Contact Phone Business
approvercontacts#.contact.phoneBusiness
Fixed Entry
genFixed e.g. Source: genFixedTEST Target: RM*{} GDS Result: RM*TEST
Cytric Source
Cytric Sources can be used in the custom field definitions.
Example:
First additional eMail
firstAdditionalEMail
Second additional eMail
secondAdditionalEMail
Location
companyBinding.cytricLocation
Division
companyBinding.cytricDivision
Airline Discount Card Type (Air France)
AirlineDiscountCardType_AF_0 AirlineDiscountCardType_AF_1 AirlineDiscountCardType_AF_2
Airline Discount Number (Air France)
AirlineDiscountCardNumber_AF_0 AirlineDiscountCardNumber_AF_1 AirlineDiscountCardNumber_AF_2
Airline Discount Valid through (Air France)
AirlineDiscountCardValidity_AF_0 AirlineDiscountCardValidity_AF_1 AirlineDiscountCardValidity_AF_2
Airline Discount Card Type (Scandinavian Airlines - SAS)
AirlineDiscountCardType_SK_0
Airline Discount Number (Scandinavian Airlines - SAS)
AirlineDiscountCardNumber_SK_0
Airline Discount Valid through (Scandinavian Airlines - SAS)
AirlineDiscountCardValidity_SK_0
Redress Number
redressNumber
Known Traveller Number
knownTravNumber
Home Address Street
home_street
Home Address Postal Code
home_zip
Home Address City
home_city
Home Address Country
home_country
Home Address Mobile number
home_mobile
Home Email
home_email
My Air Travel Preferences - Default Departure City
AirPreferences_DepartureCode
Send Confirmation eMail as
emailFormat
Business Address Company
business_company
Business Address Street
business_street
Business Address Postal Code
business_zip
Business Address City
business_city
Business Address Country
business_country
Business Address Telefax
business_fax
Emergency Contact - Relationship
emergency_relationship
Emergency Contact - Country
emergency_country
External Profil ID
externalReference
AeTM
Specification for AeTM Synchronisation
Form of payment / credit card
In the Company profile section “Interface Setup”, the fields Personal CC on, 2nd Personal CC on and 3rd Perosnal CC on are available. The synchronisation to AeTM is limited to three credit cards. A fourth credit card in a traveller profile will be not transferred to AeTM.
Synch from Faces to AeTM:
- If the “use as form of payment” is activated in Faces, the credit card in AeTM will be setup as “Airline Ticket Payment”.
- If in Faces more than one credit card is active with “use as form of payment” the first credit card will be setup as “Airline Ticket Payment“ in AeTM.
Synch form AeTM to Faces:
- The “Airline Ticket Payment” will activate the “use as form of payment“ in the Faces credit card.
- Existing “use as form of payment” in Faces will not be overridden.
General:
- If activated in AeTM, the AeTM-fields “Hotel Guarantee/Payment” and “Car Guarantee” are synchronised with the fields “Guarantee hotel” and “Guarantee car rental” in Umbrella Faces.
Login Name / Username
Synch form AeTM to Faces:
- In case of duplicate usage of a login name in the AeTM systems, Faces will automatically process the incoming profile and will create the username from the Traveller ID rather of rejecting the profile
Cytric
Specification for Cytric Synchronisation
User Access Rights
from Tenzing Faces to Cytric
- Any change of roles and/or Faces usertype (Traveller, Arranger, Approver) will also affect the Cytric roles
- No change in roles and Faces usertype will not override any existing role setup in Cytric.
- Changes of profile data's (e.g. phone, email etc.) without changing roles will not override any existing role setup in Cytric.
- Adding or changing roles will not synchronize any User Access Rights of Assignments for Travel Arrangers/Trip Approvers in the user profile. Existing Assignments setting will be deleted by changing or adding roles.
from Cytric to Faces
- No Assignments for Travel Arranger/Trip Approvers are synchronized
Rail
from Faces to Cytric
- The activation of "collect points" in the Traveller Profile will also synchronize the Railcard as "Frequent Traveller Numbers - Rail"
- DB bonus.card is not a valid card in Cytric, therefore no synchronisation will be done
- DB Card 100 is not a valid Frequent Traveller-Railcard, therefore no synchronisation will be done in case of activation "collect points"
from Cytric to Faces
- If same card is entered as Railcard and Frequent Traveller-Railcard "collect points" in Faces will be activated.
- If Card type, number or validity between Railcard and Frequent Traveller-Railcard are different, only the Railcard without activation "collect points" is synchronized. In case Frequent Traveller-Railcard is "Bonuscard Business" and other Railcard are entered both cards are synchronized.
Generic Setup Fields
only valid if Source "firstAdditionalEmail" and/or "secondAdditionalEmail" is used in the generic fields.
from Faces to Cytric
- Empty fields (no value) will not delete the "firstAdditionalEmail" and/or "secondAdditionalEmail" in Cytric.
Form of payment / credit cards
Synch from Faces to Cytric:
- If “use as form of payment” is activated in Faces, the credit card in cytric will be marked as “preferred CC”
- If more than one credit card is active with “use as form of payment” in Faces, the first credit card will be marked as “preferred CC” in Cytric
Synch from Cytric to Faces:
- The “preferred CC” in the credit card will activate the “use as form of payment “ in the Faces credit card.
- Existing “use as form of payment” in Faces will not be overridden.
The Cytric parameters in “Assign Credit Card to Vendor” are not synchronized
Login Name / Username
Synch from Cytric to Faces:
- In case of duplicate usage of a login name in the Cytric systems, Faces will automatically process the incoming profile and will create the username from the Profile ID rather of rejecting the profile