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 6 Next »

Objectives

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

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*
(if Automatic schedule)

Simple integration : 

  • "non-event" day : Every 5 minutes
  • "event" day : Every 5 minutes

Advanced integration, high performance scenario :

  • "non-event" day : Every 5 minutes
  • "event" day : Every 1 minute
Batch SizeYes10 000

Date from

No

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

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

Shipment modes 

Yes

API Key of your TIXNGO Organizer ADMIN account

Force Ticket Tax Numbers

No

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

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

Skip Ticket Tax Numbers

No

(warning) Use with caution (warning)

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

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.


Nominal behavior of the function

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

  1. have been marked as Controlled in S-360 (alongside with Access Control timestamp)

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

  3. have not been already sent to TIXNGO by this function

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