My agency: Unterschied zwischen den Versionen

Aus Faces Dokumentation
Wechseln zu: Navigation, Suche
 
Zeile 1: Zeile 1:
 +
 
== Overview ==
 
== Overview ==
  
Zeile 5: Zeile 6:
 
== Layout ==
 
== Layout ==
  
−
[[Image:TravelAgency.png|800px|Manage travel agency]]
+
[[File:TravelAgency.png|800px|Manage travel agency]]
  
 
== User Interface ==
 
== User Interface ==
Zeile 14: Zeile 15:
  
 
{|
 
{|
−
! Field  
+
|-
 +
! Field
 
! Description
 
! Description
 
|-
 
|-
Zeile 39: Zeile 41:
 
|-
 
|-
 
| Send profile updates to
 
| Send profile updates to
−
| This field indicates to which Email account an alert about an update or change will be sent. Emails would only be triggered if changes are executed by travellers or company admins.
+
| This field indicates to which Email account an alert about an update or change will be sent. Emails would only be triggered if changes are executed by travellers or company admins.  
 
If changes are done by the agency admin no email alert is send. In case of no email address is inserted, no alert emails will be sent. (Email Alert example below)
 
If changes are done by the agency admin no email alert is send. In case of no email address is inserted, no alert emails will be sent. (Email Alert example below)
 +
 
|-
 
|-
 
| Send system notifications to
 
| Send system notifications to
 
| A system notification is an email message which informs about incoming AeTM or Cytric update/creation profiles, which cannot be processed due to technical reason, e. g. Cytric Org Id or AeTM Community not existing in Faces, User login is already in use etc. An email address can be entered to which the notification should be sent.
 
| A system notification is an email message which informs about incoming AeTM or Cytric update/creation profiles, which cannot be processed due to technical reason, e. g. Cytric Org Id or AeTM Community not existing in Faces, User login is already in use etc. An email address can be entered to which the notification should be sent.
 
|}
 
|}
−
 
  
 
'''Email Alert example:'''
 
'''Email Alert example:'''
  
−
[[Image:Email Alert.PNG|700px|Email Alert]]
+
[[File:Email Alert.PNG|700px|Email Alert]]
  
 
=== Section 'Privacy policy' ===
 
=== Section 'Privacy policy' ===
 +
 
In this section, additional Privacy policy can be created and the user can be forced to re-accept the privacy policy condition within the next login. Privacy policy can be created in all different available language preferences.
 
In this section, additional Privacy policy can be created and the user can be forced to re-accept the privacy policy condition within the next login. Privacy policy can be created in all different available language preferences.
  
 
The klick on "Add new" will display a Editor in which new conditions can be created.
 
The klick on "Add new" will display a Editor in which new conditions can be created.
  
−
[[Image:Editor.PNG|500px|Editor]]
+
[[File:Editor.PNG|500px|Editor]]
  
 
''Important:''The privacy policy will be shown after the general Umbrella Faces policy.
 
''Important:''The privacy policy will be shown after the general Umbrella Faces policy.
  
−
<h3> System Settings </h3><table>
+
=== System Settings ===
−
<tr>
+
 
−
<th> Field
+
{|
−
</th>
+
|-
−
<th> Description
+
! Field
−
</th></tr>
+
! Description
−
<tr>
+
|-
−
<td> Acitve
+
| Acitve
−
</td>
+
| deactive or active agency
−
<td> deactive or active agency
+
|-
−
</td></tr>
+
| Key
−
<tr>
+
| Agency Key
−
<td> Key
+
|-
−
</td>
+
| Faces
−
<td> Agency Key
+
| activates the usage of Faces
−
</td></tr>
+
|-
−
<tr>
+
| Self-booking
−
<td> Faces
+
| activates the useage of SBT (not deployed)
−
</td>
+
|-
−
<td> activates the usage of Faces
+
| Accelerators
−
</td></tr>
+
| activates the useage of Robotic Tools
−
<tr>
+
|-
−
<td> Self-booking
+
| PCI DSS
−
</td>
+
| acitvates the useage of PCI DSS Module
−
<td> activates the useage of SBT (not deployed)
+
|-
−
</td></tr>
+
| Rail
−
<tr>
+
|
−
<td> Accelerators
+
*- = no Rail  
−
</td>
+
*AMADEUS_GERMAN = Railprovider DB (Deutsche Bahn), SBB (Swiss Railway)  
−
<td> activates the useage of Robotic Tools
+
*AMADEUS_RAIL = Railprovider DB (Deutsche Bahn), SNCF, Thalys, Swedish Railways, Trainline, Renfe, SBB, ÖBB  
−
</td></tr>
+
 
−
<tr>
+
different Formats are used in Amadeus CSX for AMADEUS_GERMAN and AMADEUS-RAIL (see Mapping)
−
<td> PCI DSS
+
 
−
</td>
+
|-
−
<td> acitvates the useage of PCI DSS Module
+
| Railmaster PCC
−
</td></tr>
+
| used Galileo Railmaster PCC
−
<tr>
+
|-
−
<td> Rail
+
| Browser-Extension
−
</td>
+
| activates the useage of Browser Extension
−
<td>
+
|-
−
<ul><li> - = no Rail</li>
+
| Profile Reminder
−
<li> AMADEUS_GERMAN = Railprovider DB (Deutsche Bahn), SBB (Swiss Railway)</li>
+
|
−
<li> AMADEUS_RAIL = Railprovider DB (Deutsche Bahn), SNCF, Thalys, Swedish Railways, Trainline, Renfe, SBB, ÖBB</li></ul>
+
|-
−
<p>different Formats are used in Amadeus CSX for AMADEUS_GERMAN and AMADEUS-RAIL (see Mapping)
+
| Loyalty Points
−
</p>
+
| no in use, will be decommissoned
−
</td></tr>
+
|-
−
<tr>
+
| Residence Information
−
<td> Railmaster PCC
+
| activates the useage of Residence Information for the Spanish market
−
</td>
+
|-
−
<td> used Galileo Railmaster PCC
+
| No. of companies
−
</td></tr>
+
| Shows the total numbers of Company profiles in the agency
−
<tr>
+
|-
−
<td> Browser-Extension
+
| No. of travellers
−
</td>
+
| Shows the total numbers of traveller profiles in the agency
−
<td> activates the useage of Browser Extension
+
|}
−
</td></tr>
 
−
<tr>
 
−
<td> Profile Reminder
 
−
</td>
 
−
<td> <span _fck_mw_customtag="true" _fck_mw_tagname="module" _fck_mw_tagtype="t" name="Profile Reminder" _fck_mw_tagattributes="name" class="fck_mw_special">activatesfckSPACEthefckSPACEuseagefckSPACEoffckSPACEProfilefckSPACEReminder</span>
 
−
</td></tr>
 
−
<tr>
 
−
<td> Loyalty Points
 
−
</td>
 
−
<td> no in use, will be decommissoned
 
−
</td></tr>
 
−
<tr>
 
−
<td> Residence Information
 
−
</td>
 
−
<td> activates the useage of Residence Information for the Spanish market
 
−
</td></tr>
 
−
<tr>
 
−
<td> No. of companies
 
−
</td>
 
−
<td> Shows the total numbers of Company profiles in the agency
 
−
</td></tr>
 
−
<tr>
 
−
<td> No. of travellers
 
−
</td>
 
−
<td> Shows the total numbers of traveller profiles in the agency
 
−
</td></tr></table>
 
  
 
=== Section 'CSX Webservice' ===
 
=== Section 'CSX Webservice' ===
  
 
{|
 
{|
 +
|-
 
! Field
 
! Field
 
! Description
 
! Description
Zeile 161: Zeile 139:
 
|-
 
|-
 
| Office ID
 
| Office ID
−
| Insert Office ID  
+
| Insert Office ID
 
|-
 
|-
 
| Org. ID
 
| Org. ID
 
| Insert the ID of the organization  
 
| Insert the ID of the organization  
−
By clicking on <Test Login> the connection to Amadeus can be tested  
+
By clicking on <Test Login> the connection to Amadeus can be tested
 +
 
 
|-
 
|-
 
| Publish passport
 
| Publish passport
−
| The Passport data
+
| The Passport data  
−
* SR DOCS: passport data, date of birth are registered as SR*DOCS in CSX
+
*SR DOCS: passport data, date of birth are registered as SR*DOCS in CSX  
−
* DOCUMENTS: passport data, date of birth are registered in the Document Section in CSX
+
*DOCUMENTS: passport data, date of birth are registered in the Document Section in CSX  
−
* BOTH: passport data, date of birth are registered as SR*DOCS and in the Document Section in CSX
+
*BOTH: passport data, date of birth are registered as SR*DOCS and in the Document Section in CSX  
 +
 
 
|-
 
|-
 
| Publish mobile-no.
 
| Publish mobile-no.
−
| The mobile number
+
| The mobile number  
−
* APM: Mobile phone of the traveler profile is entered as APM 0664600600600
+
*APM: Mobile phone of the traveler profile is entered as APM 0664600600600  
−
* LEGACY: Mobile phone of the traveler profile is entered as AP 0664600600600-M
+
*LEGACY: Mobile phone of the traveler profile is entered as AP 0664600600600-M  
 +
 
 
|}
 
|}
  
Zeile 182: Zeile 163:
  
 
{|
 
{|
−
!Field
+
|-
−
!Description
+
! Field
 +
! Description
 
|-
 
|-
 
| User name
 
| User name
−
| Interface name to Amadeus Profile Link  
+
| Interface name to Amadeus Profile Link
 
|-
 
|-
 
| Password
 
| Password
−
| Password
+
| Password  
 
By clicking on <test login> the connection to AeTM Profile Link can be tested
 
By clicking on <test login> the connection to AeTM Profile Link can be tested
−
|-
+
 
 
|}
 
|}
  
Zeile 197: Zeile 179:
  
 
{|
 
{|
−
!Field
+
|-
−
!Description
+
! Field
 +
! Description
 
|-
 
|-
 
| User name
 
| User name
−
| Galileo PCC e.g. PCC7E1N  
+
| Galileo PCC e.g. PCC7E1N
 
|-
 
|-
−
|-
+
| Host Access Profile
−
| Host Access Profile  
 
 
| Galileo HAP e.g. DynGalileoProd_7E1N
 
| Galileo HAP e.g. DynGalileoProd_7E1N
 
|-
 
|-
Zeile 211: Zeile 193:
 
|-
 
|-
 
| Password
 
| Password
−
| Password
+
| Password  
 
By clicking on <test login> the connection to Galileo can be tested
 
By clicking on <test login> the connection to Galileo can be tested
 +
 
|-
 
|-
 
| Use Travelscreen
 
| Use Travelscreen
Zeile 221: Zeile 204:
  
 
{|
 
{|
−
!Field
+
|-
−
!Description
+
! Field
 +
! Description
 
|-
 
|-
 
| Client ID
 
| Client ID
−
| Client ID name of Cytirc  
+
| Client ID name of Cytirc
 
|-
 
|-
 
| Username
 
| Username
 
| Cytric system
 
| Cytric system
−
|-  
+
|-
−
| Password
 
 
| Password
 
| Password
 +
| Password
 
By clicking on <test login> the connection to Cytric can be tested
 
By clicking on <test login> the connection to Cytric can be tested
−
|-
+
 
 
|}
 
|}
  
Zeile 239: Zeile 223:
  
 
{|
 
{|
−
!Field
+
|-
−
!Description
+
! Field
 +
! Description
 
|-
 
|-
 
| Client ID
 
| Client ID
Zeile 246: Zeile 231:
 
|-
 
|-
 
| URL
 
| URL
−
| relevant target URL for umbrella.net  
+
| relevant target URL for umbrella.net
 +
|}
 +
 
 +
Setup and configuration for umbrella.net can be found in the [http://www.umbrella.ch/doc/index.php/Tenzing_Faces#Konfiguration online documentation ].
 +
 
 +
=== Section 'Custom Field definitions' ===
 +
 
 +
On this page, additional fields can be defined, which will appear on the profiles depending on the selected type of profile. General, preferences, your team, travel documents and administration can be selected. In addition, new sections can be defined with a unique label. This selection determines, in which sections the defined field appear on the profiles.
 +
 
 +
'''Tipp:''' Inside the section the position of the relevant field can be rearranged by using the drag & drop functionality
 +
 
 +
&nbsp;
 +
 
 +
{|
 +
|-
 +
! Field
 +
! Description
 +
|-
 +
| Label
 +
| This is the title of the determined field
 +
|-
 +
| Mandate
 +
| The following obligations can be selected: O = optional, M = mandatory, CS = company-specific.
 +
|-
 +
| R/W ( visibilitiy)
 +
|
 +
*AGENCY_ONLY: the field is visible and editable only for Travel Agency Admins
 +
*COMPANY_ONLY: the field is visible and editable only for Travel Agency Admins and Company Admins
 +
*READ_ONLY: the field is always visible, but only editable for Travel Agency Admins
 +
*READ_WRITE: the field is always visible and editable
 +
 
 +
|-
 +
| CSX Prefix
 +
| Here the Amadeus prefix is entered. Possible prefixes AB, AM, AP, APE, ES, FD, FK, FT, FZ, OP, OS, PHI/G-, PCI/G-, PCO, PN, PLS, PPR, PPS, PPT, SR, ST, RM, RC, RX, RMC (Categorie Remarks), RIR).
 +
Specific's:
 +
 
 +
*OS prefix: a space is needed by using a airline code and free text (e.g. OS EK BRWD)
 +
*SR prefix: the SR prefix have to be follwow by the identifier, Airline (e.g. SRFOIDLH)
 +
 
 +
To include the profile transfer indicator in the prefix, please use:
 +
 
 +
*A&#124;(active)
 +
*S&#124;(selective)
 +
*M&#124;(mandatory)
 +
 
 +
infront of the prefix, e.g. A&#124;RM*INFO:{}
 +
 
 +
'''Special use of Profile Notes:'''
 +
 
 +
Per default all data in the Faces comment field will be published as Amadeus Profile Notes, except if a setup with PN is configured in the custom published action.
 +
 
 +
Targets:
 +
 
 +
*1&#124;PN = will publish the configured source into line number 1 in the Profile Notes
 +
*5&#124;PN = will publish the configured source into line number 5 in the Profile Notes
 +
*Source: “comment” & Target: “20&#124;PN” = will publish the complete input a the comment field started from Profile Notes line 20.
 +
 
 +
Rules/General:
 +
 
 +
*Blank Profile Notes Lines will be filled with a dot (.). Example a copy setup for Profile Line 1 and 3 is configured, in this case line number 2 will be filled with a dot.
 +
*Copy actions other than the source “comment” will be truncated by 56 characters.
 +
 
 +
|-
 +
| GWS
 +
| Here the Galileo prefix is entered. To include the line number and transfer code (R, N, O, Y) please use
 +
*10&#124;Y&#124; = Line number 10 with transfer code Y
 +
*23&#124; = line number 23 with Galileo Default transfer code
 +
*O&#124; = transfer code "O"
 +
 
 +
Example: 10&#124;Y&#124;NP.HX*{}
 +
 
 +
|-
 +
| AeTM
 +
| The index of AeTM Custom Fields and traveller profile fields Email2 and Email3
 +
|-
 +
| Cytric
 +
|
 +
*The index of Cytric Free Data Fields
 +
*The index of Cytric first and second additional Email in the traveller profile.
 +
**firstAdditionalEMail
 +
**secondAdditionalEMail 
 +
 
 +
'''Cytric: Process on Free Data File incl. pnrValue'''
 +
 
 +
The flag "P&#124;" in the Cytric source is identify the fields will process on FDF incl. “pnrValue”. If the flag has been set and an incoming-cytric.xml contains a FDF incl. “value” and “pnrValue”, Faces will automatically create a validation rule (Regex) with a list of “value” and “pnrValue”.
 +
 
 +
{|
 +
|-
 +
! Validation rule
 +
! Example
 
|-
 
|-
 +
| [L<pnrValue>=<value>
 +
| [LDL=Driving License;NI=DNI;FFIB=Iberia Plus Card;PP=Passport
 
|}
 
|}
  
−
Setup and configuration for umbrella.net can be found in the [http://www.umbrella.ch/doc/index.php/Tenzing_Faces#Konfiguration online documentation ].
+
This list will be also automatically expanded if new values and pnrValues will be delivered in the incoming-cytic.xml. Every prefix on custom fields and custom actions (copy) will only contain the value from “pnrValue”.
 +
 
 +
'''''Flag to identify a FDF incl. “pnrValue”:'''''
 +
 
 +
P|<FDF-Name>
 +
 
 +
Example:
  
−
<h3> Section 'Custom Field definitions' </h3><p>On this page, additional fields can be defined, which will appear on the profiles depending on the selected type of profile. General, preferences, your team, travel documents and administration can be selected. In addition, new sections can be defined with a unique label. This selection determines, in which sections the defined field appear on the profiles.
 
−
</p><p><b>Tipp:</b> Inside the section the position of the relevant field can be rearranged by using the drag &amp; drop functionality
 
−
</p><p>
 
−
</p>
 
−
<table>
 
−
<tr>
 
−
<th> Field
 
−
</th>
 
−
<th> Description
 
−
</th></tr>
 
−
<tr>
 
−
<td> Label
 
−
</td>
 
−
<td> This is the title of the determined field
 
−
</td></tr>
 
−
<tr>
 
−
<td> Mandate
 
−
</td>
 
−
<td> The following obligations can be selected: O = optional, M = mandatory, CS = company-specific.
 
−
</td></tr>
 
−
<tr>
 
−
<td> R/W ( visibilitiy)
 
−
</td>
 
−
<td>
 
−
<ul><li> AGENCY_ONLY: the field is visible and editable only for Travel Agency Admins </li>
 
−
<li> COMPANY_ONLY: the field is visible and editable only for Travel Agency Admins and Company Admins</li>
 
−
<li> READ_ONLY: the field is always visible, but only editable for Travel Agency Admins </li>
 
−
<li> READ_WRITE: the field is always visible and editable </li></ul>
 
−
</td></tr>
 
−
<tr>
 
−
<td> CSX Prefix
 
−
</td>
 
−
<td> Here the Amadeus prefix is entered. Possible prefixes AB, AM, AP, APE, ES, FD, FK, FT, FZ, OP, OS, PHI/G-, PCI/G-, PCO, PN, PLS, PPR, PPS, PPT, SR, ST, RM, RC, RX, RMC (Categorie Remarks), RIR).
 
−
<p>Specific's:
 
−
</p>
 
−
<ul><li>OS prefix: a space is needed by using a airline code and free text (e.g. OS EK BRWD)</li>
 
−
<li>SR prefix: the SR prefix have to be follwow by the identifier, Airline (e.g. SRFOIDLH)</li></ul>
 
−
<p>To include the profile transfer indicator in the prefix, please use:
 
−
</p>
 
−
<ul><li>A|(active)</li>
 
−
<li>S|(selective)</li>
 
−
<li>M|(mandatory)</li></ul>
 
−
<p>infront of the prefix, e.g. A|RM*INFO:{}
 
−
</p><p><b>Special use of Profile Notes:</b>
 
−
</p><p>Per default all data in the Faces comment filed will be published as Amadeus Profile Notes, except a setup with PN is configured in the custom published action.
 
−
</p><p>Targets:
 
−
</p>
 
−
<ul><li>1|PN = will publish the configured source into line number 1 in the Profile Notes</li>
 
−
<li>5|PN = will publish the configured source into line number 5 in the Profile Notes</li>
 
−
<li>Source: “comment” &amp; Target: “20|PN” = will publish the complete input a the comment field started from Profile Notes line 20.</li></ul>
 
−
<p>Rules/General:
 
−
</p>
 
−
<ul><li>Blank Profile Notes Lines will be filled with a point (.). Example a copy setup for Profile Line 1 and 3 is configured, in this case line number 2 will be filled with a point.</li>
 
−
<li>Copy actions other than the source “comment” will be truncated by 56 characters.</li></ul>
 
−
</td></tr>
 
−
<tr>
 
−
<td> GWS
 
−
</td>
 
−
<td> Here the Galileo prefix is entered. To include the line number and transfer code (R, N, O, Y) please use
 
−
<ul><li>10|Y| = Line number 10 with transfer code Y</li>
 
−
<li>23|  = line number 23 with Galileo Default transfer code</li>
 
−
<li>O|    = transfer code "O"</li></ul>
 
−
<p>Example:
 
−
10|Y|NP.HX*{}
 
−
</p>
 
−
</td></tr>
 
−
<tr>
 
−
<td> AeTM
 
−
</td>
 
−
<td> The index of AeTM Custom Fields and traveller profile fields Email2 and Email3
 
−
</td></tr>
 
−
<tr>
 
−
<td> Cytric
 
−
</td>
 
−
<td>
 
−
<ul><li>The index of Cytric Free Data Fields</li>
 
−
<li>The index of Cytric first and second additional Email in the traveller Profil.
 
−
<ul><li>firstAdditionalEMail</li>
 
−
<li>secondAdditionalEMail </li></ul></li></ul>
 
−
<p><b>Cytric: Process on Free Data File incl. pnrValue</b>
 
−
</p><p>The flag "P|" in the Cytric source is identify the fields will process on FDF incl. “pnrValue”. If the flag has been set and a incoming-cytric.xml contains a FDF incl. “value” and “pnrValue”, Faces will automatically create a validation rule (Regex) with a list of “value” and “pnrValue”.
 
−
</p>
 
−
<table>
 
−
<tr>
 
−
<th>Validation rule
 
−
</th>
 
−
<th>Example
 
−
</th></tr>
 
−
<tr>
 
−
<td>[L&lt;pnrValue&gt;=&lt;value&gt;
 
−
</td>
 
−
<td>[LDL=Driving License;NI=DNI;FFIB=Iberia Plus Card;PP=Passport
 
−
</td></tr></table>
 
−
<p>This list will be also automatically expanded if new values and pnrValues will be delivered in the incoming-cytic.xml. Every prefix on custom fields and custom action (copy) will only contain the value from “pnrValue”.
 
−
</p><p><i><b>Flag to identify a FDF incl. “pnrValue”:</b></i>
 
−
</p><p>P|&lt;FDF-Name&gt;
 
−
</p><p>Example:
 
 
P|Costcenter
 
P|Costcenter
−
</p><p><i><b>Validation:</b></i>
+
 
−
</p><p>[L=-
+
'''''Validation:'''''
−
</p><p>This validation will ensure that an empty option is available in Faces, no empty option will be create automatically. If you do not use this validation the list will automatically expanded like [LHD=Helpdesk;TR=Training;MA=Management. By using the [L=- the list will be created like [L=-;HD=Helpdesk;TR=Training;MA=Management which provides an empty option (-) in the Faces drop down.
+
 
−
</p>
+
[L=-
−
</td></tr>
+
 
−
<tr>
+
This validation will ensure that an empty option is available in Faces, no empty option will be created automatically. If you do not use this validation the list will be&nbsp;expanded&nbsp;automatically i.e. [LHD=Helpdesk;TR=Training;MA=Management. By using the [L=- the list will be created as [L=-;HD=Helpdesk;TR=Training;MA=Management which provides an empty option (-) in the Faces drop down.
−
<td> Billing
+
 
−
</td>
+
|-
−
<td> The index of umbrella.net Commercial Data
+
| Billing
−
</td></tr>
+
| The index of umbrella.net Commercial Data
−
<tr>
+
|-
−
<td> Name
+
| Name
−
</td>
+
| Is automatically created with the same value of the field “Label”. It can only be overwritten at time of creation. Existing name values cannot be modified. The value of the Name field can be used for any COPY action in the custom publish action, and is reflected in the CSV file as a designation of the field. To use the Name within a COPY action genInternal has to be included to the name for the source, e.g. genInternalAdditionalEmail.
−
<td> Is automatically created with the same value of the field “Label”. It can only be overwritten at time of creation. Existing name values cannot be modified. The value of the Name filed can be used for any COPY action in the custom publish action, and is reflected in the CSV file as designation of the field. To use the Name within a COPY action genInternal has to be included to the name for the source, e.g. genInternalAdditionalEmail.
+
|-
−
</td></tr>
+
| Internal
−
<tr>
+
| System-Admin (Support) only. The internal code can also be used for a copy in the custom pubish action to transfer generic field values from the company into a GDS traveller profile. The source must be entered with "company.geninternal<internalcode>" e.g company.geninternalmailgmt.
−
<td> Internal
+
|-
−
</td>
+
| Field
−
<td> System-Admin (Support) ony. The internal code can also be used for a copy in the custom pubish action, to transfer generic filed values from the company into a GDS traveller profile. The source must be enter with "comany.geninternal&lt;internalcode&gt;" e.g company.geninternalmailgmt.
+
| Possible values are INPUT (regular, single-line text field) and TEXTAREA (multiline text field)
−
</td></tr>
+
|-
−
<tr>
+
| Validation
−
<td> Field
+
| The generic field validation rule can be specified. The format is basically a "regular expression". Some typical examples are:  
−
</td>
+
{|
−
<td> Possible values are INPUT (regular, single-line text field) and TEXTAREA (multiline text field)
+
|-
−
</td></tr>
+
! Validation
−
<tr>
+
! Description
−
<td> Validation
+
|-
−
</td>
+
| .{5,7}
−
<td> The generic field validation rule can be specified. The format is basically a "regular expression". Some typical examples are:
+
| Any characters, but length min. 5 characters max. Be 7 characters
−
<table>
+
|-
−
<tr>
+
| [a-zA-Z]{3,}
−
<th> Validation
+
| Only letters, length min. 3 characters
−
</th>
+
|}
−
<th> Description
+
 
−
</th></tr>
+
In addition, a list of possible values can be defined. For this purpose a semicolon-separated list is entered, with leading string'[L'. Examples
−
<tr>
+
 
−
<td> .{5,7}
+
*[L;Compact;Limousine;Sedan  
−
</td>
+
*[L=-;CMP=Compact;LIM=Limousine;SED=Sedan  
−
<td> Any characters, but length min. 5 characters max. Be 7 characters
+
 
−
</td></tr>
+
The first example is written as a field value 'Sedan', the second 'SED'
−
<tr>
+
 
−
<td> [a-zA-Z]{3,}
+
|-
−
</td>
+
| Profile Type
−
<td> Only letters, length min. 3 characters
+
| A distinction is made between Traveller and Company, T (Traveller) and C (Company) for the profile type on which the profile box appears
−
</td></tr></table>
+
|}
−
<p>In addition, a list of possible values can be defined. For this purpose a semicolon-separated list is entered, with leading string'[L'.  
 
−
Examples
 
−
</p>
 
−
<ul><li> [L;Compact;Limousine;Sedan</li>
 
−
<li> [L=-;CMP=Compact;LIM=Limousine;SED=Sedan</li></ul>
 
−
<p>The first example is written as a field value 'Sedan', the second 'SED'
 
−
</p>
 
−
</td></tr>
 
−
<tr>
 
−
<td> Profile Type
 
−
</td>
 
−
<td> A distinction is made between Traveller and Company, T (Traveller) and C (Company) for the profile type on which the profile box appears
 
−
</td></tr></table>
 
  
 
=== Section 'Custom Publish Actions' ===
 
=== Section 'Custom Publish Actions' ===
  
 
{|
 
{|
 +
|-
 
! Field
 
! Field
 
! Description
 
! Description
Zeile 419: Zeile 392:
 
|-
 
|-
 
| Type of Profile
 
| Type of Profile
−
| A distinction is made between Traveller and Company, T (Traveller) and C (Company). Select the Type of Profile on which the profile box appears.
+
| A distinction is made between Traveller and Company, T (Traveller) and C (Company). Select the Type of Profile on which the profile box appears.
 
|-
 
|-
 
| Interface
 
| Interface
Zeile 431: Zeile 404:
 
|}
 
|}
  
−
The source for the COPY function company data profile can be found under [[Profile Company#Profile Actions | Company]]  
+
The source for the COPY function company data profile can be found under [[Profile_Company#Profile_Actions|Company]] The source for the COPY function Traveller data is visible at line 1 in the CSV file. If 0-n lists (FQTV or passports) are copied, either an index (passports0, passports1) can be used, or use the index placeholder '#' (# passports). The latter then copies all existing indexes.
−
The source for the COPY function Traveller data is visible at line 1 in the CSV file. If 0-n lists (FQTV or passports) are copied, either an index (passports0, passports1) can be used, or use the index placeholder '#' (# passports). The latter then copies all existing indexes.
 
  
−
FILTER examples can be found under profile [[Profile Traveller#Profile Actions|Traveller]] | and profile [[Profile Company#Profile Actions|Company]]
+
FILTER examples can be found under profile [[Profile_Traveller#Profile_Actions|Traveller]] | and profile [[Profile_Company#Profile_Actions|Company]]
  
 
== Import/export generic setup ==
 
== Import/export generic setup ==
 +
 
(available with the next release, planed 18th October 15)
 
(available with the next release, planed 18th October 15)
  
−
A export and/or import from the agency generic setup of custom field definitions and custom publish actions in a XML schema file.
+
A export and/or import from the agency generic setup of custom field definitions and custom publish actions in a XML schema file. The XML file can be used for a upload to a existing agency.
−
The XML file can be used for a upload to a existing agency.
 
  
 
== Workflows / Processes ==
 
== Workflows / Processes ==
  
−
New '''fields''' can be added just by clicking on "Add New" in the field definition section. At the bottom of the field definitons section, a new '''section''' can be added by clicking on "Add New".  
+
New '''fields''' can be added just by clicking on "Add New" in the field definition section. At the bottom of the field definitons section, a new '''section''' can be added by clicking on "Add New".
  
 
The publish actions can be added by clicking on "Add New".
 
The publish actions can be added by clicking on "Add New".

Aktuelle Version vom 10. April 2019, 15:23 Uhr

Overview

In this tab the travel agency is managed (depening on access authorization)

Layout

Manage travel agency

User Interface

Section 'Address'

All information entered here will appear by clicking on the tab "My travel agency,". This information is also displayed at the top right of the blue bar.

Field Description
Name Name of Travel Agency
Street Street of Travel Agency
PLZ Postal code
Location Location of Travel Agency
Country Country where Travel Agency is located
Phone Insert phone number of Travel Agency
URL Insert the URL of the Travel Agency
Send profile updates to This field indicates to which Email account an alert about an update or change will be sent. Emails would only be triggered if changes are executed by travellers or company admins.

If changes are done by the agency admin no email alert is send. In case of no email address is inserted, no alert emails will be sent. (Email Alert example below)

Send system notifications to A system notification is an email message which informs about incoming AeTM or Cytric update/creation profiles, which cannot be processed due to technical reason, e. g. Cytric Org Id or AeTM Community not existing in Faces, User login is already in use etc. An email address can be entered to which the notification should be sent.

Email Alert example:

Email Alert

Section 'Privacy policy'

In this section, additional Privacy policy can be created and the user can be forced to re-accept the privacy policy condition within the next login. Privacy policy can be created in all different available language preferences.

The klick on "Add new" will display a Editor in which new conditions can be created.

Editor

Important:The privacy policy will be shown after the general Umbrella Faces policy.

System Settings

Field Description
Acitve deactive or active agency
Key Agency Key
Faces activates the usage of Faces
Self-booking activates the useage of SBT (not deployed)
Accelerators activates the useage of Robotic Tools
PCI DSS acitvates the useage of PCI DSS Module
Rail
  • - = no Rail
  • AMADEUS_GERMAN = Railprovider DB (Deutsche Bahn), SBB (Swiss Railway)
  • AMADEUS_RAIL = Railprovider DB (Deutsche Bahn), SNCF, Thalys, Swedish Railways, Trainline, Renfe, SBB, ÖBB

different Formats are used in Amadeus CSX for AMADEUS_GERMAN and AMADEUS-RAIL (see Mapping)

Railmaster PCC used Galileo Railmaster PCC
Browser-Extension activates the useage of Browser Extension
Profile Reminder
Loyalty Points no in use, will be decommissoned
Residence Information activates the useage of Residence Information for the Spanish market
No. of companies Shows the total numbers of Company profiles in the agency
No. of travellers Shows the total numbers of traveller profiles in the agency

Section 'CSX Webservice'

Field Description
WS App Abot or Faces
User ID Amadeus User ID
Password Password
Accesspoint Amadeus WSAP
Office ID Insert Office ID
Org. ID Insert the ID of the organization

By clicking on <Test Login> the connection to Amadeus can be tested

Publish passport The Passport data
  • SR DOCS: passport data, date of birth are registered as SR*DOCS in CSX
  • DOCUMENTS: passport data, date of birth are registered in the Document Section in CSX
  • BOTH: passport data, date of birth are registered as SR*DOCS and in the Document Section in CSX
Publish mobile-no. The mobile number
  • APM: Mobile phone of the traveler profile is entered as APM 0664600600600
  • LEGACY: Mobile phone of the traveler profile is entered as AP 0664600600600-M

Section 'AeTM'

Field Description
User name Interface name to Amadeus Profile Link
Password Password

By clicking on <test login> the connection to AeTM Profile Link can be tested

Section 'Galileo WS'

Field Description
User name Galileo PCC e.g. PCC7E1N
Host Access Profile Galileo HAP e.g. DynGalileoProd_7E1N
PCC Galileo Pseudo City Code. e.g. 7E1N
Password Password

By clicking on <test login> the connection to Galileo can be tested

Use Travelscreen Activation of Travelscreen useage

Section 'Cytric'

Field Description
Client ID Client ID name of Cytirc
Username Cytric system
Password Password

By clicking on <test login> the connection to Cytric can be tested

Section 'umbrella.net'

Field Description
Client ID umbrella.net Client ID (Mandanten ID)
URL relevant target URL for umbrella.net

Setup and configuration for umbrella.net can be found in the online documentation .

Section 'Custom Field definitions'

On this page, additional fields can be defined, which will appear on the profiles depending on the selected type of profile. General, preferences, your team, travel documents and administration can be selected. In addition, new sections can be defined with a unique label. This selection determines, in which sections the defined field appear on the profiles.

Tipp: Inside the section the position of the relevant field can be rearranged by using the drag & drop functionality

 

Field Description
Label This is the title of the determined field
Mandate The following obligations can be selected: O = optional, M = mandatory, CS = company-specific.
R/W ( visibilitiy)
  • AGENCY_ONLY: the field is visible and editable only for Travel Agency Admins
  • COMPANY_ONLY: the field is visible and editable only for Travel Agency Admins and Company Admins
  • READ_ONLY: the field is always visible, but only editable for Travel Agency Admins
  • READ_WRITE: the field is always visible and editable
CSX Prefix Here the Amadeus prefix is entered. Possible prefixes AB, AM, AP, APE, ES, FD, FK, FT, FZ, OP, OS, PHI/G-, PCI/G-, PCO, PN, PLS, PPR, PPS, PPT, SR, ST, RM, RC, RX, RMC (Categorie Remarks), RIR).

Specific's:

  • OS prefix: a space is needed by using a airline code and free text (e.g. OS EK BRWD)
  • SR prefix: the SR prefix have to be follwow by the identifier, Airline (e.g. SRFOIDLH)

To include the profile transfer indicator in the prefix, please use:

  • A|(active)
  • S|(selective)
  • M|(mandatory)

infront of the prefix, e.g. A|RM*INFO:{}

Special use of Profile Notes:

Per default all data in the Faces comment field will be published as Amadeus Profile Notes, except if a setup with PN is configured in the custom published action.

Targets:

  • 1|PN = will publish the configured source into line number 1 in the Profile Notes
  • 5|PN = will publish the configured source into line number 5 in the Profile Notes
  • Source: “comment” & Target: “20|PN” = will publish the complete input a the comment field started from Profile Notes line 20.

Rules/General:

  • Blank Profile Notes Lines will be filled with a dot (.). Example a copy setup for Profile Line 1 and 3 is configured, in this case line number 2 will be filled with a dot.
  • Copy actions other than the source “comment” will be truncated by 56 characters.
GWS Here the Galileo prefix is entered. To include the line number and transfer code (R, N, O, Y) please use
  • 10|Y| = Line number 10 with transfer code Y
  • 23| = line number 23 with Galileo Default transfer code
  • O| = transfer code "O"

Example: 10|Y|NP.HX*{}

AeTM The index of AeTM Custom Fields and traveller profile fields Email2 and Email3
Cytric
  • The index of Cytric Free Data Fields
  • The index of Cytric first and second additional Email in the traveller profile.
    • firstAdditionalEMail
    • secondAdditionalEMail

Cytric: Process on Free Data File incl. pnrValue

The flag "P|" in the Cytric source is identify the fields will process on FDF incl. “pnrValue”. If the flag has been set and an incoming-cytric.xml contains a FDF incl. “value” and “pnrValue”, Faces will automatically create a validation rule (Regex) with a list of “value” and “pnrValue”.

Validation rule Example
[L<pnrValue>=<value> [LDL=Driving License;NI=DNI;FFIB=Iberia Plus Card;PP=Passport

This list will be also automatically expanded if new values and pnrValues will be delivered in the incoming-cytic.xml. Every prefix on custom fields and custom actions (copy) will only contain the value from “pnrValue”.

Flag to identify a FDF incl. “pnrValue”:

P|<FDF-Name>

Example:

P|Costcenter

Validation:

[L=-

This validation will ensure that an empty option is available in Faces, no empty option will be created automatically. If you do not use this validation the list will be expanded automatically i.e. [LHD=Helpdesk;TR=Training;MA=Management. By using the [L=- the list will be created as [L=-;HD=Helpdesk;TR=Training;MA=Management which provides an empty option (-) in the Faces drop down.

Billing The index of umbrella.net Commercial Data
Name Is automatically created with the same value of the field “Label”. It can only be overwritten at time of creation. Existing name values cannot be modified. The value of the Name field can be used for any COPY action in the custom publish action, and is reflected in the CSV file as a designation of the field. To use the Name within a COPY action genInternal has to be included to the name for the source, e.g. genInternalAdditionalEmail.
Internal System-Admin (Support) only. The internal code can also be used for a copy in the custom pubish action to transfer generic field values from the company into a GDS traveller profile. The source must be entered with "company.geninternal<internalcode>" e.g company.geninternalmailgmt.
Field Possible values are INPUT (regular, single-line text field) and TEXTAREA (multiline text field)
Validation The generic field validation rule can be specified. The format is basically a "regular expression". Some typical examples are:
Validation Description
.{5,7} Any characters, but length min. 5 characters max. Be 7 characters
[a-zA-Z]{3,} Only letters, length min. 3 characters

In addition, a list of possible values can be defined. For this purpose a semicolon-separated list is entered, with leading string'[L'. Examples

  • [L;Compact;Limousine;Sedan
  • [L=-;CMP=Compact;LIM=Limousine;SED=Sedan

The first example is written as a field value 'Sedan', the second 'SED'

Profile Type A distinction is made between Traveller and Company, T (Traveller) and C (Company) for the profile type on which the profile box appears

Section 'Custom Publish Actions'

Field Description
Action Select COPY or FILTER for your action
Type of Profile A distinction is made between Traveller and Company, T (Traveller) and C (Company). Select the Type of Profile on which the profile box appears.
Interface Indicate which interfaces the action will affect
Source Indicate the source respectively the corresponding filter.
Target Indicate the target or insert a free text if using the filter function.

The source for the COPY function company data profile can be found under Company The source for the COPY function Traveller data is visible at line 1 in the CSV file. If 0-n lists (FQTV or passports) are copied, either an index (passports0, passports1) can be used, or use the index placeholder '#' (# passports). The latter then copies all existing indexes.

FILTER examples can be found under profile Traveller | and profile Company

Import/export generic setup

(available with the next release, planed 18th October 15)

A export and/or import from the agency generic setup of custom field definitions and custom publish actions in a XML schema file. The XML file can be used for a upload to a existing agency.

Workflows / Processes

New fields can be added just by clicking on "Add New" in the field definition section. At the bottom of the field definitons section, a new section can be added by clicking on "Add New".

The publish actions can be added by clicking on "Add New".

Von «http://doc.umbrella.ch/tzdoc/index.php?title=My_agency&oldid=1545»