Versions Compared

Old Version 1

changes.mady.by.user jbo (Unlicensed)

Saved on

compared with

New Version 2

changes.mady.by.user jbo (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This function retrieves information from TIXnGO about the ticket (status, holder) and stores it inside SecuTix. 

With FIFASTX-2770, we aligned the statuses and the screens between TIXNGO and S-360 :

  • with the lifecycle mode, we synchronize the tickets from a "business" perspective 
  • with the history mode (legacy behaviour), we synchronize the tickets from a "blockchain transaction" perspective


Table of Contents

Ticket statuses

History mode (legacy behaviour)

  • 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

Lifecycle mode (new behaviour)

  • Possible Statuses : INJECTED, DOWNLOADED, ASSIGNED, CONTROLLED, PENDING_TRANSFER, FAILURE_TRANSFER, TRANSFERRED, BT_ACTIVATED, MANUAL_ACTIVATED, OFFLINE_ACTIVATED, ONLINE_ACTIVATED, DELETION_PENDING, DELETED, ACTIVATED, DEACTIVATED, DEFAULT, INVALID, PENDING, FAILURE
  • Possible Actions & States : Does not exist anymore. Replaced by Business Statuses
S360 Ticket Status

S360 Blockchain Status (history)

S360 Blockchain Status (lifecycle)

Not printedNANA

Printed







(after injection) INJECTED

No Action/Status as long as the user does not have a wallet 

(after injection) INJECTED

(after download) RECEIVED

Action/Status : Inject/Confirmed

(after download) DOWNLOADED

(after assignment) RECEIVED (warning) Holder/Assignee fields are set

Action/Status : Inject/Confirmed 

(after assignment) ASSIGNED

(after transfer initiated) TRANSFER_PENDING

Action/Status : Inject/Confirmed

(after transfer initiated) PENDING_TRANFER

(after transfer cancelled by sender) RECEIVED

(after transfer rejected by receiver) RECEIVED

Action/Status : Inject/Confirmed

(after transfer cancelled by sender) FAILURE_TRANSFER

(after transfer rejected by receiver) FAILURE_TRANSFER

(after transfer accepted) TRANSFERRED

Action/Status : Transfer/Confirmed

(after transfer accepted) TRANSFERRED

(after ticket offline activation) ACTIVATED

(after ticket online activation) ACTIVATED

(after ticket manual activation) ACTIVATED

(after ticket bluetooth/beacon activation) ACTIVATED

No specific Action/Status

(after ticket offline activation) OFFLINE_ACTIVATED

(after ticket online activation) ONLINE_ACTIVATED

(after ticket manual activation) MANUAL_ACTIVATED

(after ticket bluetooth/beacon activation) BT_ACTIVATED

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

(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

→ 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

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 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

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

History mode

How to activate enable it?

In the custom parameters, you can use TIXNGO_LIFECYCLE_MODE=history

(question) what happens if we don't ?

Mapping > blockchain_ticket

DB ColumnTicket details 
INSTIT_CODENA
TICKET_IDticketId
ORGANIZ_ID????
BLOCKCHAIN_TICKET_ID????
BLOCKCHAIN_TICKET_STATUSlegacyStatus
TICKET_LAST_UPDATElastUpdateTimestamp
ACTIVATION_DATEactivation.date
ACTIVATION_TYPEactivation.method
ACTIVATION_PHONE_MODELactivation.device
ACTIVATION_DURATION????
ACTIVATION_BEACON????
OWNER_EMAILspectatorDetails.email
OWNER_TITLEspectatorDetails.title
OWNER_FIRSTNAMEspectatorDetails.firstName
OWNER_LASTNAMEspectatorDetails.lastName
OWNER_PHONE_NUMBERspectatorDetails.phoneNumber
OWNER_ID_NUMBERspectatorDetails.idCardNumber
OWNER_BIRTH_DATEspectatorDetails.dateOfBirth
OWNER_COUNTRY_CODEspectatorDetails.nationality
OWNER_LANGUAGENot mapped
OWNER_INFO1Not mapped
OWNER_INFO2Not mapped
OWNER_INFO3Not mapped
OWNER_INFO4Not mapped
ASSIGNEE_EMAILNot mapped
ASSIGNEE_FIRSTNAMEspectatorDetails.ticketHolder.identity.firstName
ASSIGNEE_LASTNAMEspectatorDetails.ticketHolder.identity.lastName
ASSIGNEE_PHONE_NUMBERspectatorDetails.ticketHolder.identity.phoneNumber
ASSIGNEE_ID_NUMBERspectatorDetails.ticketHolder.identity.idCardNumber
ASSIGNEE_BIRTH_DATEspectatorDetails.ticketHolder.identity.dateOfBirth
ASSIGNEE_LANGUAGENot mapped
ASSIGNEE_NATIONALITYspectatorDetails.ticketHolder.identity.nationality
ASSIGNEE_INFO1spectatorDetails.ticketHolder.identity.extraInfo1
ASSIGNEE_INFO2spectatorDetails.ticketHolder.identity.extraInfo2
ASSIGNEE_INFO3spectatorDetails.ticketHolder.identity.extraInfo3
ASSIGNEE_INFO4spectatorDetails.ticketHolder.identity.extraInfo4
USR_LOG_INA
DTE_LOG_INA
USR_LOG_LUNA
DTE_LOG_LUNA
VERSIONNA

Mapping > blockchain_ticket_trans_log

DB ColumnTicket details Ticket details 
INSTIT_CODENA
TICKET_IDticketId
ORGANIZ_ID???
TRANSACTION_LOG_ID???
TRANSACTION_ID???
TRANSACTION_DATE???
ACTIONhistory[i].txType
STATEhistory[i].txStatus
BLOCKCHAIN_TICKET_STATUSNot mapped
INFONot mapped
ADDITIONAL INFONot mapped
SENDER_EMAILhistory[i].srcSpectator.email
SENDER_PHONE_NUMBERhistory[i].srcSpectator.phoneNumber
RECIPIENT_EMAILhistory[i].dstSpectator.email
RECIPIENT_PHONE_NUMBERhistory[i].dstSpectator.phoneNumber
RECIPIENT_TITLEhistory[i].dstSpectator.title
RECIPIENT_FIRSTNAMEhistory[i].dstSpectator.firstName
RECIPIENT_LASTNAMEhistory[i].dstSpectator.lastName
RECIPIENT_ID_NUMBERhistory[i].dstSpectator.idCardNumber
RECIPIENT_BIRTH_DATEhistory[i].dstSpectator.dateOfBirth
RECIPIENT_COUNTRY_CODEhistory[i].dstSpectator.nationality
RECIPIENT_LANGUAGENot mapped
RECIPIENT_INFO1Not mapped
RECIPIENT_INFO2Not mapped
RECIPIENT_INFO3Not mapped
RECIPIENT_INFO4Not mapped
USR_LOG_INA
DTE_LOG_INA
USR_LOG_LUNA
DTE_LOG_LUNA
VERSIONNA