Objectives

Synchronize TIXNGO tickets with S-360 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 to create the "Retrieve tickets" function?

If the TIXNGO interface has not been created or configured, please refer to S-360 to TIXNGO interface > 0. Initial setup of the interface

Once the basic configuration is completed, go the Schedules screen and click New button.

Select the function you want, in this case "Retrieve ticket status from TIXNGO" to add and Click Next.

How to configure the "Retrieve tickets" function?

Field

Mandatory

Description

Internal name

Yes

Name for this function

Launch

Yes

Either Manual or Automatic

In case Automatic is selected, it's necessary to configure Frequency, Start, End

Frequency

Yes*

Mandatory only if Automatic schedule

	Simple integration	Advanced integration (high perf)
"non-event" day	Every 5 minutes	To be discussed with SECUTIX experts
"event" day	Every 5 minutes	To be discussed with SECUTIX experts

Batch Size

Yes

	Simple integration	Advanced integration (high perf)
"non-event" day	1 000	To be discussed with SECUTIX experts
"event" day	1 000	To be discussed with SECUTIX experts

Pagination Key

No

Self-sufficient parameter that is not meant to be overridden by an Operator

For the first execution, keep it empty.
For the next executions, this parameter will be automatically filled by TIXNGO.

Skip Ticket Tax Numbers

No

List of Ticket Numbers aka Tax numbers (comma separated) that will be ignored if they're returned by TIXNGO

File to upload

No

Will parse the attached file and process it as it was to TIXNGO

USE WITH CAUTION Not suitable for day-2-day operations with an Automatic schedule
In case of an automatic schedule, the same tickets will be sent over and over again.

Browser not supported