Objectives

Synchronize S-360 Controlled Ticket Status (in this case Controlled) with TIXNGO Ticket Statuswith TIXNGO Ticket Status.

Nominal behavior of the function

How does the function collect & process controlled tickets?

The function will only process tickets matching the following criteria:

1. Tickets have been previously injected into TIXNGO.
2. Tickets are matching function schedule filters (shipment mode, …)
3. Tickets have not been already processed by any other TIXNGO Push Controlled function.

How does the function synchronize the controlled tickets into TIXNGO?

• If the controlled tickets are successfully synced with TIXNGO, tickets won’t be processed again by the function.
• If there is an error preventing all tickets to be synced with TIXNGO properly (TIXNGO or TIXNGO interface errors), tickets will be processed again during the upcoming executions. 
  NOTE: An error indicating the origin of the failure will be present in the function execution logs.
• If most of the tickets are successfully synced but a few encounter errors, the successfully synced tickets won’t be processed again. The function will continue to show an error until a corrective action is performed: either by actively skipping the problematic tickets OR by fixing the issue.
  NOTE: An error indicating the origin of the failure will be present in the function execution logs.

How to create or configure the Push Controlled function?

...

Function has been provisioned, the configuration can start.

...

Image Modified	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 Every 5 minutes "event" day Every 5 minutes Every 1 minute
	Batch Size	Yes	10 000
	Shipment modes	Yes	API Key of your TIXNGO Organizer ADMIN account
	Date from	No

USE WITH CAUTION Not suitable for Day-2-Day normal operations with an Automatic schedule

	If the date is specified (format DD/MM/YY hh:mm), the function will send to TIXNGO all controlled tickets as if the last successful execution of the function was at the given date. 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.
Force Ticket Tax Numbers	No

USE WITH CAUTION Not suitable for Day-2-Day normal operations with an Automatic schedule

	List of Ticket Numbers aka Tax numbers (comma separated) to be sent to TIXNGO (ie the function will only push thee ones from the list). 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.
Skip Ticket Tax Numbers	No

USE WITH CAUTION

List of Ticket Numbers aka Tax numbers (comma separated) to NOT be sent to TIXNGO (ie the function ignores them) 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 ignored over and over again.
Notify spectator	No
File to upload	No	USE WITH CAUTION Not suitable for Day-2-Day normal operations with an Automatic schedule Will parse the attached file and send the list of tickets to TIXNGO In case of an automatic schedule, the same tickets will be sent over and over again.

Nominal behavior of the function

The function will only push to TIXNGO, the already injected tickets that

...

comply with the selected filters (Shipment Modes, Force Tickets, Skip Tickets)

Specific behaviour the Push Controlled function

...