Cards
- Glossary
- 1. I work with the UID
- 2. I work with the cardnumber
- 3. I work both with the cardnumber and the UID
- FAQ
Glossary
- UID: physical ID of a card, the chip number
- Cardnumber: the number associated with the card, often printed on it, or encoded in a barcode
- Empty field: field with null value, "" or "null"
- Our system: our database of cards
1. I work with the UID
- I set a value (during creation, or if the field was previously empty)
- I change the value (there was a previous value, I set a new one)
- I empty the value (there was a previous value, I set it to empty)
=> The cardnumber is filled automatically if the card is known in our system
If the card is not known, the cardnumber value does not change
=> The cardnumber is filled automatically if the card is known in our system
If the card is not known, the cardnumber value does not change
=> The cardnumber is emptied
2. I work with the cardnumber
- I set a value (during creation, or if the field was previously empty)
- I change the value (there was a previous value, I set a new one)
- I empty the value (there was a previous value, I set it to empty)
=> The UID is filled automatically if the card is known in our system
If the card is not known, the UID value does not change
=> The UID is filled automatically if the card is known in our system
If the card is not known, the UID value does not change
=> The UID is emptied
3. I work both with the cardnumber and the UID
- I set a value, cardnumber or UID (during creation, or if the fields were previously empty)
- I set or modify the 2 values, cardnumber and UID
- I modify one of the two values, and let the other unchanged
- I modify one of the 2 values, and empty the other
- I empty one of the two values
- I empty the two values
- My account has been set up in "OPEN" mode (accept all cards), does it change something?
- If I clear the value of the cardnumber, is it saved in the previouscardnumber field?
=> The other field (cardnumber or UID) is filled automatically if the card is known in our system
If the card is not known, the other value stays empty
=> If the card is not known in our system (neither the UID nor the carndumber), the 2 values defined are used
=> If the UID is known in our system, the cardnumber value will be the one found in our system
=> If the cardnumber is known but not the UID, the UID value will be the one found in our system
=> The previous rule (3.b) applies
=> If this value (UID or cardnumber) is not known in our system, it will still be used, but the other field stays empty
=> If this value is known, the other field will take the value found in our system
=> We consider that the card has been disassociated, so the 2 values are emptied
=> The card is disassociated, the 2 values are emptied
FAQ
This does not change the behavior discribed here
Yes, each time the value of cardnumber changes, the previous value, if not empty, is saved in previouscardnumber.
ADELYA (c) 2005-2024 24-05_master_3036