Table of Contents |
---|
...
1. User Access Rights
From Faces to Cytric
- Any change of roles and/or Faces usertype (Traveller, 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
...
- No Assignments for Travel Arranger/Trip Approvers are synchronized
2. 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"
...
- 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
3. Generic Setup Fields
Only valid if Source "firstAdditionalEmail" and/or "secondAdditionalEmail" is used in the generic fields
...
- Empty fields (no value) will not delete the "firstAdditionalEmail" and/or "secondAdditionalEmail" in Cytric
4. Form of payment / credit cards
Synch from Faces to Cytric
...
The Cytric parameters in “Assign Credit Card to Vendor” are not synchronized
5. Login Name / Username
Synch from Cytric to Faces
...