Ticket Configuration V4
What is a “Ticket Configuration” rule ?
In the current version of TIXNGO, ticket behaviors are managed using 'groups' (activation, transfer, design) defined within the injection template and customized at the event level.
With TIXNGO V4, ticket behaviors will transition to being managed through Ticket Configuration, now organized into specific Ticket Rules defined at the organizer level.
This shift brings greater visibility, encourages reusability, and simplifies management. Once a rule is created, it can be linked to multiple events, streamlining workflows and ensuring consistent ticket behavior across all of an organizer's events.
New Rule Types
Rules inherited from TIXNGO V3
To maintain full functionality and preserve TIXNGO's existing capabilities, the following rules have been migrated, adjusted, and renamed:
Activation (formerly known as Activation Group) will still host the rules defining how the QR is revealed → V4 Activation rules
Design (formerly known as Design Group) will still host the rules defining how the ticket looks like in the Wallet → V4 Design rules
Usage (formerly known as Transfer Group) will host the rules defining how the ticket can be used in the Wallet → V4 Usage rules
TIXNGO V4 Exclusive rules
With the new Rules approach in V4, we're laying the groundwork for features that were previously impossible.
For TIXNGO V4 roll-out, we delivered two new exclusive features based on new rule types:
Data Collection rule, allowing organizers to customize the data collection process for Ticket Holders → V4 Data Collection rules
Email rule, allowing organizers to customize the emails sent for a specific audience → V4 Email rules
New “Rule” Approach
The new 'Rule' approach introduces a streamlined process for defining and managing ticket behaviors, providing greater flexibility and control at the organizer level.
This approach separates the What? (ie, the rule definition) from the 'Where is it applied?' (ie, the rule association) for improved clarity and ease of use.
Rule Definition
Rules will be defined in the Ticket Configuration screen
For each Rule Type
a DEFAULT rule will be provisioned (the rule is customizable by organizer)
the rule name must be unique (for this organizer)
Rule Association
Rules can be automatically associated to events during ticket injection
Or can also be manually associated to events
There is no limit on the number of Rules that can be associated with a given event, regardless of the rule type.
As of TIXNGO V4 roll-out, it’s impossible to dissociate a rule from an event. In other wordyou are not required to use them.
The rules will be available at event level, but their actual application depends entirely on how you configure your injection template to associate each ticket with the appropriate rule.
New set of straightforward screens
Ticket Configuration screen
A brand new screen, named “Ticket Configuration” will be available to ADMIN and TIXNGO_SUPPORT back-office users, allowing them to centrally manage, create & update rules.
Edit Event screen
Ticket Configuration V4 rules will be accessible under their respective sections (one section per type) in the Edit Event > Ticket Rules tab.
Ticket Rules tab
Rule association
Export/import of rules
In order to simplify onboarding or testing in pre-production before making changes in production, all the ticket rules can be easily exported from one environment and then imported in another.
During import in the target environment:
new rules will be added;
existing rules (with the same name) will be updated.
Importing rules will NEVER delete any existing rule in the target environment.
We DO NOT RECOMMEND making any manual modifications to the export files content, except maybe removing lines, in order to avoid formatting errors or incorrect data that could impact event operations. Any manual modification is done AT YOUR OWN RISK.
If you need to remove some rules (lines) before re-importing, DO NOT USE EXCEL as it may silently alter the format or content of certain fields. We recommend removing lines with a text editor, for instance Visual Studio Code with CSV extensions.