Objectives
Synchronize TIXNGO tickets with S-360 Controlled tickets by retrieving the latest tickets updates from TIXNGO and storing TIXNGO-specific information, such as Mobile Ticket Status, Ticket Ownership and Ticket Beneficiaries (ie Assignee) into S-360.
Nominal behavior of the function
"Retrieve ticket status from TIXNGO" function does not support simultaneous executions.
In other words, at any time, ONLY ONE function must be Active, regardless if tickets are injected, cancelled or controlled from multiple S-360 organizations.
How does the function collect & process TIXNGO tickets?
The function will only process tickets that are returned by TIXNGO diff endpoint.
How does the function synchronize TIXNGO tickets into S-360?
Since the lifecycle introduction and the additional adjustments, the mapping is fixed and predictable, meaning that S-360 receives only what is necessary for its functioning and what is visible in the back-office screens.
For more details about the exact mapping used, please refer to S-360 to TIXNGO interface > 4.1 Which TIXNGO ticket data is synced back to S-360 ?
Since the "Contact Creation & Distribution" introduction, on top of the standard Ticket details refresh mechanism, it's possible to transform TIXNGO ticket ownership into S-360 cultural contact assignment.
For more details about the criteria around Contact Creation & Cultural Contact Assignment, please refer to S-360 to TIXNGO interface > 4.2 Cultural Contact Creation & Distribution
How does it work?
The "Retrieve ticket status from TIXnGO", also known as "Feedback interface" retrieves information from TIXnGO about the ticket holder and stores it inside S-360.
Only the batch size not already handled tickets are retrieved from TIXnGO.
Only one function "retrieve ticket status from TIXnGO" must run for a given organizer, regardless if tickets are injected from multiple organizations.
Recommended frequency
Every 5 minutes.
Pagination key
Do not touch this value if you do not know what you are doing.
Skip ticket
A non-mandatory parameter in which you can add all the ticket IDs that you want to skip.
Batch size
Recommended value: 1000