Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Current »

Upcoming change to Greeting & Title on traveller profiles

Currently available fields:

 

With the upcoming change, these fields will be deprecated. We are planning to remove these deprecated fields (gender & title) at some point next year. The exact date will be communicated again, and well in advance of course.

During the deprecation period, both the old and new data structures ("greeting", see below) will be available in the API. However, you should only use either structure in a Create / Update request (as soon as "greeting" is included, "gender" and "title" will be ignored).

New fields available will be:

 

Depending on the travel agency setup, not all combinations of common / formal title are supported by the Faces UI. It's best to consult with the travel agency on their setup to ensure a consistent user experience.

The common titles referenced in the swagger definition are generally valid for every agency.

Please refer to the following table:

 

Formal Title
Title Structure "Default"
Title Structure "Compound" *
Master(error) Not supported(tick) Supported
Mx(error) Not supported(tick) Supported
DR(tick) Supported(tick) Supported
PROF(tick) Supported(tick) Supported 
Rev(error) Not supported(tick) Supported
Sir(error) Not supported(tick) Supported
Lord(error) Not supported(tick) Supported
Lady(error) Not supported(tick) Supported

* Titles are supported, if no commonTitle is set. Since for "Compound" the UI is only using a single drop-down it is not possible to display a title such as MR DR.

Using compoundTitle vs commonTitle & formalTitle

Umbrella Faces in it's backend always stores the compoundTitle, but transparently derives common and formal title in API requests using the following general format: compoundTitle = trim(commonTitle + " " + formalTitle).

When updating a profile in Umbrella Faces, it is important to only send either the compoundTitle or commonTitle / formalTitle but not both structures. If both structures are retrieved, the compoundTitle takes priority and commonTitle / formalTitle are ignored.

 Example compoundTitle values
compoundTitle in API request
resulting commonTitle
resulting formalTitle
Remarks
MSMS  
MR DRMRDRIf the travel agency is using title structure "Compound", the stored value will not be visible in the UI since "MR DR" is unsupported
MISS LadyMISSLady

Not supported by the Faces UI - would show as follows:

  • Title Structure Default: "Lady" would not be visible in the UI
  • Title Structure Compound: Title in the UI would be shown as "-" since a combination of "MISS Lady is unsupported
PROF MRSUNDEFINEDPROF MRS

Invalid request results in incorrect parsing since the commonTitle is to be sent as the first part of the compoundTitle

PROFUNDEFINEDPROF 
RevUNDEFINEDRevIf the travel agency is using title structure "Default", the stored value will not be visible in the UI
  • No labels