Tickets V4 Bulk-update

Tickets V4 Bulk-update

Overview

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

overview.jpg
Ticket bulk update menu entry.

Bulk-update wizard

The ticket bulk update is a powerful tool with lots of capabilities. To help you use it easily and saf

  1. Select tickets to update

  2. Select what to update

  3. Validate & run

Step 1: Select the tickets to update

You have 2 ways to target the ticket: by using filters or using a csv file.

All updates are not available depending on the selection mode used. Please see below for more details.

1a. Use filters

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

bulk-update step 1.jpg
Bulk-update tickets from filters

The available filters are:

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

1b. Use a CSV file

Upload a file csv with all the tickets you want to update by using their ticket numbers

bulk-update by csv.jpg
Bulk-update tickets from csv file

When providing a CSV file, you can update tickets of several events at once.


Step 2: Select what to update

After select tickets in step 1, you can select what needs to be updated:

  • Ticket Configuration rule

  • Seating detail value

  • Metadata value

  • Custom flow value

Only one update option can be selected and applied at a time in this step.

2a. Ticket configuration rule

This option allows users to update the configuration rule applied to targeted tickets.

Config rule.jpg
Bulk-update configuration rule by using filters
  • Rule type: Select the type of rule to update. Options include:

    • Design

    • Data collection

    • Usage

    • Email

    • Activation

      • Note: Tickets that already activated cannot be updated to new activation rule

  • From Rule name:

    • If you selected tickets using filters (1a):

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

      • User selects the rule currently applied to tickets.

      • Note:

        • When user select rule type = 'Activation', some rule name will be disabled (grey out) if there are:

          • Activation method = 'Offline'

          • AND activation time ≤ current time.

    • If you selected tickets using a CSV file (1b):

      • This field is be disabled because tickets may come from different events.

  • To Rule name:

    • If you selected tickets using filters (1a):

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

      • User selects the new rule to be appli

      • Note:

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

    • If you selected tickets using a CSV file (1b):

      • Dropdown list of all rule names available for the selected type of that organizer

      • User selects the new rule to be applied.

  • 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

2b. Seating Detail value

You have a lot of tickets with the “Gate” value need to be updated? Here is your solution:

seating details.jpg
Bulk-update Seating Details value

This option allow user to update a new value to the selected Seating Details for all tickets

  • Seating Details: Display a list of seating details label:

    • External Entrance

    • Gate

    • Area

    • Level

    • Block

    • Row

    • Seat

  • Current value:

    • If a current value is provided, only tickets with that value will be updated to new value

    • If no current value provided, all targeted tickets will be updated to new value

  • New value: Input the new value you want the tickets will be updated to

2c. Metadata value

You have a lot of tickets with the Tickets Detail metadata display an outdated value?

Metadata update.jpg
Bulk-update Metadata value

This option allows users to update the value of a specific key within a selected section of the ticket metadata for targeted tickets.

  • Section: Select the section in the ticket metadata to update:

    • Main

    • Extra

    • Hidden

  • Update key: Enter an existing key from the selected section of the ticket metadata.

  • Language: Select the language for the value you want to update.

  • New value: Enter the new value to apply to the targeted tickets

2d. Custom flow

You have injected tickets with custom flow and there is a key display wrong values? This is your solution.

10239b30-9ca0-41bd-9cf6-214bc65583b3.jpg
Bulk update a custom flow value

This option allows users to update the value of a specific custom flow key for targeted tickets.

  • Update key: Enter an existing key from a custom flow.

  • New value: Enter the new value to apply to the targeted tickets

To update only a flow value for tickets having, use the CSV mode to select tickets to update. The Reporting endpoint - Full tickets list can easily help you find the tickets you need.

Step 3: Validate and apply change

overview step 3.jpg
Step 3 overview & validation

Validate information

After finish step 2, you will be redirected to the last step of bulk-update.

This step will display all the information you have selected in the last 2 steps; it also displays the number of tickets will be affected

image-20251210-095559.png
Selected information and Estimated number of affected tickets

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

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.

  • Enter a ticket number in the input field.

  • Click Run Single Ticket Update.

Note: The entered ticket number must match the filters above, otherwise the update will not run.

image-20251210-095847.png

In that mode, only this single ticke

Apply change

After validating all the information above, finally you can apply change for all tickets.

To avoid a wrong manipulation and undesired massive update, you will have to tick the “I confirm….” box before being able to use the “Update all tickets” button.

image-20251210-100344.png

You can also tick in other check box for following option you want:

  • If you want to continue update for tickets? tick in the “Stay on this screen after update is complete” unless it will navigate you to the History table

  • To make sure the ticket holders aware about their tickets are updated tick in the “Send user a push notification when their tickets are updated”

History table

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

history.jpg
Table showing past bulk updates

Table Overview

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

  • Target ticket: Display the selected target ticket (by filters or By a CSV file)

  • Event: Ticket’s event name (null if target filter= by a CSV file)

  • 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

  • Actions: When user click in the icon, the screen popup information related to the batch of bulk-update including:

    • Targets:

      • If the target is CSV, user can download that CSV file from the popup

      • If the target is filters, it will display all the selected filter

    • Update content

      •  

image-20251210-102004.png
Target = CSV
image-20251210-102326.png
Target = filters