Credit Card Billing address
The latest Faces version implements new standard fields for credit cards “billing address” on travellers and companies.
We have added the new fields to the ‘Customization Standard Fields’ in the agency setups so that the use of the new fields can be decided individually for each agency or company.
As soon as the new fields have been activated on the agency or company, each credit card has the option of entering a billing address.
Functional Details:
- The "State" field will be displayed in the same way as for the company address when the country "United State of America", "Canada" or "Mexico" is selected and contains the state selection.
- The function "Copy profile..." in the company profile will also copy the billing address into the new profile
- The billing address will also support CSV file export & import, therefore new headers are available
- sortedCreditcards(#).street
- sortedCreditcards(#).street2
- sortedCreditcards(#).zip
- sortedCreditcards(#).place
- sortedCreditcards(#).state
- sortedCreditcards(#).country
- Mapping to target systems: Concur, Cytric, Deem, GetThere, Farelogix, Sabre Mapping
Specification of Synchronisatons:
Target System | Comments/Details |
---|---|
Concur | existing logic, if no billing address is available, the company address is sent as Concur Credit card billing address. This means that the synchronisation from Concur to Faces saves the company address as the Faces credit card billing address in the traveller profile. If the sources for Concur are configured in custom fields, the values of the custom field overwrite the new standard mapping Sources for Credit Card billing address
|
Deem | If the sources for Deem are configured in custom fields, the values of the custom field overwrite the new standard mapping Sources for Credit Card billing address
|
Sabre | If the billing address is not used in the agency/company, but a target system is used which has a mapping to the billing addresses, the address details are saved in the background and also synchronised to Sabre. FILTER: //PaymentForm/PaymentCard/Address |
Flexible Validation of Emergency Contact Information
We have implemented enhancements to improve the handling of emergency contact details provided by external systems (such as Concur and Cytric), which may only contain partial information.
Umbrella Faces has always validated whether the first name, surname and phone number are entered in the emergency contact. We have implemented this validation for the Customize Standard Fields. This enables flexible control per agency and company as to whether the emergency contact should be checked for completeness.
Examples of Configurations:
- All Fields Mandatory if Entered: If any emergency contact detail (e.g., phone) is entered, all marked mandatory fields must be filled. CURRENT BEHAVIOUR!!!
- Conditional Mandatory Fields: Agencies can set specific field pairs (e.g., first name and phone) as mandatory if one is completed.
Note. Profiles with only Emergency Contact / Email cannot be saved without providing Firstname, Lastname and Phone or Emergency Contact fields which are set to mandatroy at the customized standard fields.
Relabelling of Airline alliances
As already announced in our previous release note the drop down of the Frequent flyer airlines will be changed. The airline alliances
- Miles & More
- Sky Team
- One World
will be relabelled to
- Lufthansa (Austrian, Swiss)
- KLM Royal Dutch Airlines
- British Airways
today:
tomorrow:
Note: Where before the alliance carriers appeared at the top, with the enhancement the airlines British Airways, Lufthansa (Austrian, Swiss) and KLM Royal Dutch Airlines will be shown in true alphabetical order
Amendment to the Publishing for Airline Alliances
Changes made for synchronisation to
- Cytric
- Scandinavian Airlines has joined the Sky Team, therefore the publishing to Cytric has been changed to send "Use Number also for: Sky Team" instead of "Star Alliance"
- Worldspan
- Czech airlines are no longer part of the Skyteam alliance - therefore they we have excluded whenever DL or KL carrier is present in the profile
Identification Card / Expiry Date
We’ve added a new configuration option for the Identification Card / Expiry Date field in the Customize Standard Field section. Previously, only Identification Cards and Identification Card / Issue Date were configurable with options for Optional, Mandatory, Hidden, and Read Only. Now, agencies can also configure Identification Card / Expiry Date with these same override options.