Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Tickets status in S-360 is CANCELLED or INVALIDATED
  2. Tickets have been previously injected into TIXNGO.
  3. Tickets are matching function schedule filters (shipment mode, …)
  4. Tickets have not been already processed by any other TIXNGO Push Cancelled function.
  5. If tickets have been already processed by another TIXNGO Push Cancelled function, tickets will be re-processed seamlessly if their respective invalidation reasons have been updated.

How does the function synchronize

...

the cancelled/invalidated tickets into TIXNGO?

  • If cancelled/invalidated tickets are successfully synced with TIXNGO, tickets won’t be processed again by the function
    NOTE: Already synced tickets can be processed again by the function,
    • if the function is configured to send all tickets since a specific date by using the "Date from" parameter
    • if the function is configured to force a specific list of tickets by using the "Force Ticket Tax Numbers" parameter
  • If cancelled/invalidated tickets are successfully synced with TIXNGO, tickets will be processed again by the function only if their invalidation reason has been updated.
  • 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.

...

Select the function you want, in this case "Push cancelled and invalidated tickets" to add and Click Next.

image-2024-6-24_16-27-9.pngImage Added

Function has been provisioned, the configuration can start.

  • 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?

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 "Push controlled tickets" to add and Click Next.

image-2024-6-24_16-27-9.pngImage Modified

Function has been provisioned, the configuration can start.

Image Removed

Recommended frequency

...

Image Added

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 SizeYes1 000

Shipment modes 

Yes

List of shipment modes used by the tickets to be sent to TIXNGO (ie the function will only push tickets using the shipments modes from the list).

Date from

Image Removed

...

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 the 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 will ignore 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 spectatorNoDo not use it if you don't understand clearly the usage, it may trigger thousands of unwanted notifications on remote cell phones.

...

File to upload

No

Will parse the attached file and send the list of tickets to TIXNGO

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

Batch size

...

Ticket visibility rule

S-360 is pushing cancelled and invalidated tickets using an TIXnGI Api parameter called showDeletedTicket which defines its visibility.

...