View Source

As already stated in CSV-File, a traveller CSV can either be downloaded or uploaded directly on the company profile or via the profile center.

Basic tips on how to create and or update traveller profiles using a CSV:

The minimum fields that have to be present in a CSV file to be able to create a profile in Umbrella Faces are the following standard fields:

metadata.action	uuid	username	email	gender	name	firstname	company.uuid	company.name
Metadata / Action	uuid	Username	E-mail	Greeting	Surname as in Passport	First name as in Passport	Company / uuid	Company / Company name
SAVE	1f6eff8d-1b84-4db6-b757-ed3d8254f211	Knowledgina	knowledge@base.ch	U	Base-Traveller	Knowledge	f86ac325-49e5-43c4-8552-8baafa166791	Knowledge Base Co.
SAVE		New-User	knowledge@base.com	MR	Doe	John	f86ac325-49e5-43c4-8552-8baafa166791	Knowledge Base Co.

Please note that:

The first line in the CSV is the header line (these also serve as the additional general sources)
The second line in the CSV is the actual name of the field in Faces (to help users understand which value should be filled in in which field and what the corresponding source is. The first and second lines must always be present in the CSV as well as their labels
For a traveller profile to be created, a company profile must first be created in Faces.
The uuid is automatically generated by the system after a profile has been successfully created. It is visible by downloading the traveller CSV (see the profile of Knowledgina in the above example). The uuid has to be kept in the CSV for updates to take place.
For new profiles, the uuid has to be left blank (see New-User above)
For a profile being newly created, the metadata action SAVE( used for create and updates) has to be given in along with the other values. Either company uuid and company name can be given or just the company uuid. There is also an option to give in the company profile number/ record locator but it is not mandatory either.
To delete a profile, insert the metadata action DELETE

Using a CSV to create profiles in OBEs (AeTM, Cytric Atriis etc) using profiles that already existed in Faces *****

If an AeTM profile is created from an existing Faces Profile, the CSV-files must contains the following columns:

Column	Discription	Value
sortedTravelGroups0.groupId	Travel groups / Main travel group	Community-Code, sortedAetmRoles0.community is always the Home-Community for the traveller
sortedTravelGroups1.groupId,sortedTravelGroups2.groupId, etc.	Travel groups / Further travel group	further Communities, it can be done any numbers of communities (numbering: sortedTravelGroups"X")
sortedTravelGroups0.role ,sortedTravelGroups1.role ,sortedTravelGroups2.role, etc.	Travel groups / Role	AeTM Roles: TRAVELER PRINCIPAL_TRAVEL_ARRANGER APPOINTED TRAVEL_ARRANGER TRAVEL_APPROVER FALLBACK_APPROVER
sortedPublishStates1.id.publishtarget	Target system	Insert the value "AETM" for a transmission into AeTM
sortedPublishStates1.recordlocator	Target system identification number/name	AeTM Login Name

To merge the existing AeTM profile with an existing Faces Profil, the AeTM Login name must be entered. In case of empty "sortedPublishStates1.recordlocator" a new AeTM profile is created.