TIXnGO is the lading secure mobile wallet solution provided by the SecuTix company.
Please refer to this page for the functionalities of the product.
The document describes the features and the setup steps of the interface between SecuTix 360 and TIXnGO
As for SecuTix 360, the TixNGo system is perceived as an external printing system. Tickets injected into TIXnGO are considered as printed.
To set it up:
1.) In Organization/Tools/Interfaces create a new External Printing Interface of type "TIXnGO".
2.) Fill in the API URL provided by TIXnGO in the URL fiekd. It must end by organizer/tickets
3.) Fill in the username provided by TIXnGO (I guess the value does not matter)
4.) In the password field, fill in the API key provided by TIXnGO
5.) Inject some test tickets.
The field "Email notification...." allows you to receive emails when one of the asynchronous processes described below is failing.
The ticket injection process pushes the designated tickets to the TIXnGO system, then to the wallets of the final users.
To activate it, create a schedule to choose which tickets to process.
Every 5 minutes.
Recommended value : 1000
As this schedule must mark some tickets as printed, as if it had been done by a point of sales, you must set up (once) the sales channel and point of sales codes that will be used for that task.
Many filtering options exist : by product(s), by performance(s), by tariff or category code... They are all cumulative (AND logical relation)
This one is exclusive of all the other ones. If a file number (file id)
Please enter here one or many of the following values, separated by commas
FIRSTNAME,LASTNAME,BIRTHDATE,ID_NUMBER,COUNTRY_CODE,BIRTH_REGION,BIRTH_PLACE
Only the tickets having those beneficiary's values filled will be sent to TIXnGO.
Will send the mainApplicant flag to true to TIXnGO only when the beneficiary's first name, last name and email (and NOT the cultural contact's) are matching those of the buyer.
If this box is checked, the tickets won't be sent to TIXnGO.
/wiki/spaces/CF/pages/40576543
By default, the tickets are assigned to the cultural contact, with fallback to the purchaser contact..
But, IF the tickets has been reprinted, it will be assigned to its last known holder, as retrieved from TIXnGO.
The tickets are pushed ordered by ticket id. This likely means that ticket from a same order will come together.
This batch pushes the cancelled and invalidated tickets to TIXnGO.
It does not offer a lot of filtering possibilities.
The tickets extracted are all the ones updated (cancelled/invalidated) since the last execution ending OK or Warning.
Every 5 minutes.
This value allows to override the date of the last execution OK or Warning. If you keep it defined in a regular execution, the same tickets will be extracted and pushed over and over.
Keep it empty.
This batch pushes the controlled status of the tickets to TIXnGO
The tickets extracted are all the ones updated (controlled) since the last execution ending OK or Warning.
Every 5 minutes.
This value allows to override the date of the last execution OK or Warning. If you keep it defined in a regular execution, the same tickets will be extracted and pushed over and over.
Keep it empty.
This function retrieves information from TIXnGO about the ticket holder and stores it inside SecuTix.
Only the batch size not already handled tickets are retrieved from TIXnGO
Every 5 minutes.
Do not touch this value if you do not know what you are doing.
Recommended value: 500