Kategorie:Cytric: Unterschied zwischen den Versionen

Aus Faces Dokumentation
Wechseln zu: Navigation, Suche
(User Access Rights)
 
(7 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 4: Zeile 4:
  
 
'''from Tenzing Faces to Cytric'''
 
'''from Tenzing Faces to Cytric'''
*The creation of a Traveller Profile including the type Arranger will create the role "Travel Arranger (restricted)" in the Cytric User Profile.
+
* Any change of roles and/or Faces usertype (Traveler, Arranger, Approver) will also affect the Cytric roles
*A Administrator of a specific company with a linked Traveller profile is need to create the a Travel Arranger (restricted with Profile Admin) or Travel Arranger. The activation of "delete/create traveller" will create a Travel Arranger the deactivation of "delete/create travellers" will create a Travel Arranger (restricted with Profile Admin).  
+
* No change in roles and Faces usertype will not override any existing role setup in Cytric.
*The modification/creation (save button) will also synchronize the linked traveller profile.
+
* Changes of profile data's (e.g. phone, email etc.) without changing roles will not override any existing role setup in Cytric.
*In case of the modification of the User Access Rights, Assignments for Travel Arrangers/Trip Approvers in the user profile in Cytric will '''not''' be synchronized to Faces. A new "Save" in Faces Traveller Profile will not override this modification in Cytric. If the Administrator Profile is "Saved" in Faces the User Access Rights, Assignments for Travel Arrangers/Trip Approvers are overridden.
+
* Adding or changing roles will not synchronize any User Access Rights of Assignments for Travel Arrangers/Trip Approvers in the user profile. Existing Assignments setting will be deleted by changing or adding roles.  
*The deactivation of the type traveller will exclude the role "Booker"
+
 
 
 
'''from Cytric to Faces'''
 
'''from Cytric to Faces'''
*The User Right Access Travel Arranger, Travel Arranger (restricted Profile Admin), Travel Arranger (restricted) will synchronize a Traveller Profil including the type Arranger in Faces.
 
*No Administrator Profiles are created
 
 
*No Assignments for Travel Arranger/Trip Approvers are synchronized
 
*No Assignments for Travel Arranger/Trip Approvers are synchronized
  
 +
== Rail ==
  
'''coming soon with the next release'''''
+
'''from Faces to Cytric'''
 
+
*The activation of "collect points" in the Traveller Profile will also synchronize the Railcard as "Frequent Traveller Numbers - Rail"
'''from Tenzing Faces to Cytric'''
+
*DB bonus.card is not a valid card in Cytric, therefore no synchronisation will be done
* A deletion of a role will be not synchronised to Cytric
+
*DB Card 100 is not a valid Frequent Traveller-Railcard, therefore no synchronisation will be done in case of activation "collect points"
* The role in Cytric will only be deleted if the Cytric role and Faces-Usertype (Traveler, Arranger, Approver) is deactivated
 
* In case of the modification of the User Access Rights, Assignments for Travel Arrangers/Trip Approvers in the user profile in Cytric will '''not''' be synchronized to Faces. A new "Save" in Faces Traveller Profile will not override this modification in Cytric.
 
  
 
'''from Cytric to Faces'''
 
'''from Cytric to Faces'''
*No Assignments for Travel Arranger/Trip Approvers are synchronized
+
*If same card is entered as Railcard and Frequent Traveller-Railcard "collect points" in Faces will be activated.
 +
*If Card type, number or validity between Railcard and Frequent Traveller-Railcard are different, only the Railcard without activation "collect points" is synchronized. In case Frequent Traveller-Railcard is "Bonuscard Business" and other Railcard are entered both cards are synchronized.
  
== Rail ==
+
== Generic Setup Fields ==
 +
only valid if Source "firstAdditionalEmail" and/or "secondAdditionalEmail" is used in the generic fields.
  
 
'''from Faces to Cytric'''
 
'''from Faces to Cytric'''
*The activation of "Collect Points" in the Traveller Profile will also synchronize the Railcard as "Frequent Traveller Numbers - Rail"
+
*Empty fields (no value) will not delete the "firstAdditionalEmail" and/or "secondAdditionalEmail" in Cytric.
*DB bonus.card is not a valid card in Cytric, therefore no synchronisation will be done
 
  
'''from Cytric to Faces'''
+
<h2> Form of payment / credit cards </h2><p><i>Synch from Faces to Cytric:</i></p><ul><li>If “use as form of payment” is activated in Faces, the credit card in cytric will be marked as “preferred CC”</li><li>If more than one credit card is active with “use as form of payment” in Faces, the first credit card will be marked as “preferred CC” in Cytric</li></ul>
*If a Frequent Traveller Numbers - Rail is present the "Collect Points" in Faces will be activated.
+
<p><i>Synch from Cytric to Faces:</i>
 +
</p>
 +
<ul><li>The “preferred CC” in the credit card will activate the “use as form of payment “ in the Faces credit card. </li>
 +
<li>Existing “use as form of payment” in Faces will not be overridden.</li></ul>
 +
<p>The Cytric parameters in “Assign Credit Card to Vendor” are not synchronized
 +
</p>
 +
<h2> Government Id and Visa</h2>
 +
<p><i>Synch from Cytric to Faces:</i></p>
 +
<p>If Government ID Passport "Country of Citizenship" is empty, the "Issue Country" will be published as Passport nationality.
 +
</p>
 +
<p><i>Synch from Faces to Cytric:</i></p>
 +
<p>If Passport Issue Country is empty, the "Nationality" will be published as Goverment ID Passport "Issue Country".</p>

Aktuelle Version vom 11. September 2017, 12:35 Uhr

Specification for Cytric Synchronisation

User Access Rights

from Tenzing Faces to Cytric

  • Any change of roles and/or Faces usertype (Traveler, Arranger, Approver) will also affect the Cytric roles
  • No change in roles and Faces usertype will not override any existing role setup in Cytric.
  • Changes of profile data's (e.g. phone, email etc.) without changing roles will not override any existing role setup in Cytric.
  • Adding or changing roles will not synchronize any User Access Rights of Assignments for Travel Arrangers/Trip Approvers in the user profile. Existing Assignments setting will be deleted by changing or adding roles.

from Cytric to Faces

  • No Assignments for Travel Arranger/Trip Approvers are synchronized

Rail

from Faces to Cytric

  • The activation of "collect points" in the Traveller Profile will also synchronize the Railcard as "Frequent Traveller Numbers - Rail"
  • DB bonus.card is not a valid card in Cytric, therefore no synchronisation will be done
  • DB Card 100 is not a valid Frequent Traveller-Railcard, therefore no synchronisation will be done in case of activation "collect points"

from Cytric to Faces

  • If same card is entered as Railcard and Frequent Traveller-Railcard "collect points" in Faces will be activated.
  • If Card type, number or validity between Railcard and Frequent Traveller-Railcard are different, only the Railcard without activation "collect points" is synchronized. In case Frequent Traveller-Railcard is "Bonuscard Business" and other Railcard are entered both cards are synchronized.

Generic Setup Fields

only valid if Source "firstAdditionalEmail" and/or "secondAdditionalEmail" is used in the generic fields.

from Faces to Cytric

  • Empty fields (no value) will not delete the "firstAdditionalEmail" and/or "secondAdditionalEmail" in Cytric.

Form of payment / credit cards

Synch from Faces to Cytric:

  • If “use as form of payment” is activated in Faces, the credit card in cytric will be marked as “preferred CC”
  • If more than one credit card is active with “use as form of payment” in Faces, the first credit card will be marked as “preferred CC” in Cytric

Synch from Cytric to Faces:

  • The “preferred CC” in the credit card will activate the “use as form of payment “ in the Faces credit card.
  • Existing “use as form of payment” in Faces will not be overridden.

The Cytric parameters in “Assign Credit Card to Vendor” are not synchronized

Government Id and Visa

Synch from Cytric to Faces:

If Government ID Passport "Country of Citizenship" is empty, the "Issue Country" will be published as Passport nationality.

Synch from Faces to Cytric:

If Passport Issue Country is empty, the "Nationality" will be published as Goverment ID Passport "Issue Country".

Seiten in der Kategorie «Cytric»

Diese Kategorie enthält nur die folgende Seite.