...
- If same card is entered as Railcard and Frequent Traveller-Railcard, "collect points" will be activated in Faces
- 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 another Railcard is entered, both cards are synchronized
3.
...
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
...
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
...
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
...
4. Login Name / Username
...
From Cytric to Faces
- In case of duplicate usage of a login name in the Cytric systems, Faces will automatically process the incoming profile and will create the username from the Profile ID rather of rejecting the profile
5. Middlename
From Faces to Cytric.
- Faces sends the middle name as pers.data/Middlename and Pass/Middlename and this has the effect that if a different middle name is entered directly in Cytric under passport details, then this will be overwritten
From Cytric to Faces
- If passport/middlename und pers.data/middlename are both filled out in Cytric, we read from the per.data/middlename
- If only one middle name has been given in, we read the name from either the personal data section or the passport details