Release Note - 28. July 2025

Read from Concur by company

As of today, profiles from Concur can be imported into Faces via:

• A change of the Last Modified Date (LMD) in Concur combined with our polling mechanism

• CSV import using Read from Profile

With the new feature “Read from Concur” it is possible to import Concur profiles by using the regular polling mechanism (4 times a hour).

The Profile Center “Import” offers the possibility to request the import of profile within the next polling run.

Open

Note:

• Import can only run if no profiles are linked to the company profile

• Interface Setup needs to be configured (Refresh token, Travelconfig ID, Org/Unit Division (optional))

Concur Source - additional Emails

New source can be used to synchronize additional Emails to/from Concur

Note: the Faces standard mapping synchronises the traveler email into Email 1 and with the already existing Source “EmailPersonal” Email 2 can be pushed.

CSV Export includes Timestamp

A timestamp beside the label to all CSV exports and import error CSV are added

Format: YYYY-MM-DDTHH-MM_travellers (Timezone = UTC)

e.g. 2025-07-22T08_39_travellers

Custom fields - data inconsistencies - Correction 1st September 2025

There are data inconsistencies in your Umbrella Faces profiles because the profile type in custom field was changed after data was entered. For example, the "Random Blue" custom field was initially available for both "Companies" and "Travelers." Data was entered under "Travelers," but then the profile type was changed to only "Company."

As a result, the "Random Blue" field no longer appears in the Traveler profile, but the data still syncs to the target system.

Open

Therefore, for consistencies Umbrella will change the profile type to “-“ for all custom fields on 1^st September 2025 for which the situation occurs.

• If the stored value in the profiles is correct, no action is needed

• If the stored value in the profile is incorrect or unwanted, please manually remove the values or use the CSV export/import option.

Once this is completed, the profile type can be reverted to the preferred profile type (Company or Traveler).

Please note: It is not possible to change the profile type from e.g. “-“ to “Company” in case a traveler still has data stored in the custom field. The system will generate a message, e.g. “Field RandomBlue still has a value stored on 1 traveller profile(s)”

Amadeus - new format for Frequent flyer cards (EK and TK only)

We have been informed from Amadeus and several Agencies that Frequent flyer cards from EK and TK needs a SR*FQTV instead of FFN (which is our standard).
To solve this please add the following on your agency setup.

use the following FILTER:

Version “Tenzing”:
Source:

• //frequentTravellerSection[frequentTravellerInformation/frequentTravellerIdentification/airlineCode='EK']

• //frequentTravellerSection[frequentTravellerInformation/frequentTravellerIdentification/airlineCode='TK']

Version “Tenzing V2”: 
Source:

//Customer/ExternalCustLoyalty[@ProgramID='TK']

//Customer/ExternalCustLoyalty[@ProgramID='EK']

add the COPY

Source:

• {tf:replace(flightmemberships#.allianceCode,"TK=FQTV;EK=FQTV"),flightmemberships#.allianceCode,flightmemberships#.allianceCode,flightmemberships#.membernumber}

Target:

• A|SR*{}{}/{}{}

2FA Reset Request Procedure

Please be reminded that any request for a 2FA reset must be submitted using the official reset form. The form must be signed by the user who is requesting the reset.
Forms signed by other users (e.g. managers or colleagues) will not be accepted. This process is in place to ensure the security and integrity of user accounts.