Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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:

...

  • TRAVELER
  • PRINCIPAL_TRAVEL_ARRANGER
  • APPOINTED TRAVEL_ARRANGER
  • TRAVEL_APPROVER
  • FALLBACK_APPROVER

...

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.