Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Objectives

Synchronize S-360 Controlled Ticket Status with 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?

Go the Schedules screen and click New button. Select the function you want, in this case "Push controlled tickets" to add and Click Next.

image-2024-6-24_16-27-9.png

Function has been provisioned, the configuration can start.

FieldMandatoryDescription

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 integrationAdvanced integration (high perf)
"non-event" day Every 5 minutesEvery 5 minutes
"event" dayEvery 5 minutesEvery 1 minute
Batch SizeYes10 000

Shipment modes 

Yes

API Key of your TIXNGO Organizer ADMIN account

Date from

No


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.

(warning) USE WITH CAUTION (warning) 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

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

(warning) USE WITH CAUTION (warning) 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

List of Ticket Numbers aka Tax numbers (comma separated) to NOT be sent to TIXNGO (ie the function ignores them)

(warning) USE WITH CAUTION (warning) 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 spectatorNo
File to upload

No

(warning) USE WITH CAUTION (warning) 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.

Specific behaviour the Push Controlled function

Under the hood, the Push Controlled function supports now Long Run with Multithreading

This process is now multithreading and interruptible.


This batch pushes the controlled status of the tickets to TIXnGO

In case of an automatic schedule, the same tickets will be sent over and over again.





  • No labels