Introduction to Tickets V4 Bulk-update

Introduction to Tickets V4 Bulk-update

Overview

Tickets bulk update is available from the Backoffice main menu, in the Tickets section, under the entry Ticket config bulk update entry. This screen is enable to ADMIN,TIXNGO_SUPPORT, BASIC, and MODERATOR users

image-20251008-115831.png
Ticket bulk update menu entry.

Simply click on the New bulk update button to start configuring your bulk update.

image-20251001-095918.png
New bulk update screen with filters and rule selection to update

Past bulk update are recorded and are visible from the History table

image-20251001-095701.png
Past bulk updates are displayed in a table

Bulk-update configuration

image-20250929-032132.png

This screen is composed of 3 parts:

Tickets filtering

This allows users to narrow down the set of tickets that need to be updated.

image-20250929-075527.png
“Tickets filter” area
  • Event (mandatory):

    • Select the event for which ticket rules needs to be updated.

    • Only one event can be chosen at a time.

    • All other filters (Tariff, Contingent, Seat Category, File Number) will be loaded based on the selected event.

  • Tariff:

    • Dropdown list showing tariffs that belong to the chosen event.

    • Requires an event to be selected first.

  • Contingent:

    • Dropdown list showing contingents that belong to the chosen event.

    • Requires an event to be selected first.

  • Seat Category:

    • Dropdown list showing seat categories that belong to the chosen event.

    • Requires an event to be selected first.

  • File number:

    • Input field for entering the file number of a ticket belonging to the chosen event.

    • If the file number entered does not belong to the selected event, bulk-update will not be allowed.

Tickets rule selection

image-20251118-033812.png
Part of the bulk update screen defining which rule to update

 

Rule selection:

  • Rule type: Select the type of rule to update. Options include:

    • Design

    • Data collection

    • Usage

    • Email

    • Activation (Current not available, this option will be available in the near future)

  • From Rule name:

    • Dropdown list of rule names available for the selected type and linked with the chosen event.

    • User selects the rule currently applied to tickets.

  • To Rule name:

    • Dropdown list of rule names available for the selected type and linked with the chosen event.

    • User selects the new rule to be applied.

    • Note: The rule selected in the “From Rule Name” field will not appear in the “To Rule Name” list.

Action:

  • Check updated ticket count”: Displays the number of tickets that will be updated based on the filters and rules selected.

  • View detail”: Shows the details of the current rule and how it will be updated.

image-20251001-102115.png
Popup allowing to compare the old and new rule to make sure of the rule selection

Single ticket update

This function allows users to run a test update on a single ticket. It is useful for validating the update before applying it to a large set.

  • To use this feature, tick the checkbox “Single ticket update for validation”.

  • Enter a ticket number in the input field.

  • Click Run Single Ticket Update.

Note: The

image-20250929-094538.png

In that mode, only this single ticket will be updated. You can then open the ticket in a separate tab and make sure the result matches your expectations.

Run Bulk-update

Once all required fields are selected and the update details reviewed:

→ Click Apply Change for All Tickets to proceed.

image-20251001-094334.png

A confirmation popup will appear, displaying the number of tickets to be updated.

We put a hard limit of maximum 20,000 tickets that can be updated at once. If you need to update more tickets, please proceed in several batches using filters (e.g. contingent by contingent).

History table

The History table provides a clear overview of all bulk-update actions, along with detailed information for each update.

image-20251001-102528.png

Table Overview

Each row in the history table represents one bulk-update action. The following information is displayed for each record:

  • Event: Ticket’s event name

  • Tariff: Ticket’s Tariff name

  • Contingent: Ticket’s Contingent name

  • Seat Category: Ticket’s Seat Category name

  • File number: Ticket’s File number

  • Rule type: Ticket’s type of rule

  • From rule name: Current ticket’s rule applied

  • To rule name: Expected ticket’s rule updated to

  • Estimation: The estimated number of tickets will be affected for this batch of bulk-update

  • Actual: The actual number of tickets are affected for this batch of bulk-update

  • Updated by: User’s email does bulk-update

  • Start updated time: Start time of the update process

  • End updated time: End time of the update process

© TIXNGO 2023 - Login