This function retrieves information from TIXnGO about the ticket (status, holder) and stores it inside SecuTix.
With the lifecycle implementation, we aligned the statuses and the screens between TIXNGO and S-360 and synchronize the tickets from a "business" perspective
...
S360 Ticket Status | TIXNGO Ticket Status |
---|
Not printed | NA. The ticket does not exist in TIXNGO |
Printed
| - (after injection) INJECTED
- (after download) DOWNLOADED
- (after assignment) ASSIGNED
- (after transfer initiated) PENDING_TRANFER
- (after transfer cancelled by sender) FAILURE_TRANSFER
- (after transfer rejected by receiver) FAILURE_TRANSFER
- (after transfer accepted) TRANSFERRED
- (after ticket activation) XXX_ACTIVATED (OFFLINE_ACTIVATED, ONLINE_ACTIVATED, MANUAL_ACTIVATED, BT_ACTIVATED)
|
Controlled → ACS control → Ticket check (BO)External Access Control or S-360 Ticket Check | - (after control before feedback from TIXNGO) XYZ_ACTIVATED where XYZ is the activation method used
- (after control and feedback from TIXNGO) CONTROLLED
|
Invalidated
→ Reprint ticket → Ticket Invalidation, Reprint from the back-office Post ticket on resale | If the ticket was never sent to TIXNGO → NA but if the ticket was already existing in TIXNGO ... - DELETION_PENDING (after sending the "invalidated status to TIXNGO and receiving feedback from TIXNGO)
- DELETED (after successful blockchain deletion and feedback from TIXNGO)
If the ticket was never sent to TIXNGO → NA |
Cancelled → Cancel ticket (manually or by batch) | If the ticket was never sent to TIXNGO → NA but if the ticket was already existing in TIXNGO ... - DELETION_PENDING (after sending the "cancelled/invalidated" status to TIXNGO and receiving feedback from TIXNGO)
- DELETED (after successful blockchain deletion and feedback from TIXNGO)
If the ticket was never sent to TIXNGO → NA |
What and how we synchronize ticket details ?
...
Ui expand |
---|
|
DEPRECATED : History ModeWith the history mode (legacy behaviour), we synchronized the tickets from a "blockchain transaction" perspective. Since Lifecycle generalization, this mode has been deprecated and is not available to be used. - Possible Statuses (tixngo.legacyStatus) : INJECTED, RECEIVED, ACTIVATED, TRANSFER_PENDING, TRANSFERRED, CONTROLLED, DELETION_PENDING, DELETED
- Possible Actions : INJECT, TRANSFER, DELETE, BURN
- Possible States : PENDING, CONFIRMED, KO, DELETION_PENDING, DELETED, REGISTRATION_PENDING, CANCELLED, FAILED
S360 Ticket Status | S360 Blockchain Status (history) |
---|
Not printed | NA | Printed
| (after injection) INJECTED No Action/Status as long as the user does not have a wallet | (after download) RECEIVED Action/Status : Inject/Confirmed | (after assignment) RECEIVED Holder/Assignee fields are set Action/Status : Inject/Confirmed | (after transfer initiated) TRANSFER_PENDING Action/Status : Inject/Confirmed | (after transfer cancelled by sender) RECEIVED ... or ... (after transfer rejected by receiver) RECEIVED Action/Status : Inject/Confirmed | (after transfer accepted) TRANSFERRED Action/Status : Transfer/Confirmed | (after ticket activation) ACTIVATED No specific Action/Status | Controlled → ACS control → Ticket check (BO) | (after control BUT before feedback from TIXNGO) ACTIVATED (after control and feedback from TIXNGO) CONTROLLED No specific Action/Status | Invalidated → Reprint ticket → Post ticket on resale | If the ticket was already existing in TIXNGO ... - DELETION_PENDING (after sending the "cancelled/invalidated" status to TIXNGO and receiving feedback from TIXNGO)
- DELETED (after successful blockchain deletion and feedback from TIXNGO)
If the ticket was never sent to TIXNGO → NA | Cancelled → Cancel ticket (manually or by batch) | If the ticket was already existing in TIXNGO ... - DELETION_PENDING (after sending the "cancelled/invalidated" status to TIXNGO and receiving feedback from TIXNGO)
- DELETED (after successful blockchain deletion and feedback from TIXNGO)
If the ticket was never sent to TIXNGO → NA |
|