Table of contents

Big bangs
- Introducing the capability to override some settings at event level
Cool new features
Small new features

Product release notes

Product features

S-360 FEEDBACK INTERFACE

A more targetted way to retrieve tickets from TIXNGO and synchronize only meaningful and tickets-oriented tickets updates (ie change of ownership, assignment, put on resale, transfer, ....)
By default, "Event-centric" updates on tickets (TIXNGO events changes are not synced back to S-360) won't be returned to S-360.

Configuration key: diff.ignore-on-event-update

If TIXNGO is only integrated with S-360: diff.ignore-on-event-update must be set to true

If TIXNGO is integrated with other tools/products consuming the organizer tickets end-point, diff.ignore-on-event-update must be set to false

TIX2-2782 - Getting issue details... STATUS

Less is better, preparing the Feedback interface "summer body" by removing the ticket details that are not used in S-360.
Extend S-360 lifecycle mode (customer param "TIXNGO_LIFECYCLE_MODE=lifecycle") and get rid of the legacy status and history object by appling the following customer parameter additionalDiffParameters=lightPayload=true

Recommendations

If you're already in Lifecycle mode, you can proactively add the parameter to the S-360 interface.

If you're not using the Lifecycle mode of the feedback interface, this parameter is not needed.

TIX2-2153 - Getting issue details... STATUS

Event operation improvements

TIX2-2799 - Bigger font size of number of tickets on the green screen

Increased ticket number size on the green screen: The number of tickets displayed on the green screen has been enlarged to improve readability. This change takes into account factors such as luminosity and phone size, making it easier for stewards to read the ticket numbers.

Admintool UX improvement

TIX2-2734 - make sure we can't change the activation time of already activated tickets

Activation groups with past activation times are automatically disabled in the AdminTool. A tooltip is displayed when hovering over the disabled field, informing users that editing is not possible due to the past activation date and time. Additionally, all past date and time options are disabled in the activation date-time picker.

Wallet user app language in the admintool

TIX2-2729 - The user's application language in the spectator list

The app language selected by the wallet user will be now displayed in the Spectator list and support screens in the TIXNGO adminTool. The new field will be also part the of the exported list of fields in the CSV export. For users of the the S-360 and TIXNGO feedback interface this new data point will be also available in the S-360 reporting domains.

Tickets in different location yellow banner

TIX2-2661 - Tickets in different locations are getting a yellow banner

In some case a wallet owner can have several tickets with those tickets being in a different location (e.g. :Gate/block) When this feature is enabled the wallet owner will get (on top on the different location pop-up already existing) a yellow banner always displayed recommending the user to transfer the tickets being a different location to avoid issues at the access control.

How to enable it ?

A new admin tool setting key has been introduced: "Banner on event cells for different-gates/blocks" to enable/disable the feature.
A Crowdin-label for adjusting the banner message is also available.

Setting key in the admin tool	Crowdin label

Please note that when both yellow banners are activated "different location" yellow banner and "transfer reminder" yellow banner. the different location banner has an highest priority meaning that the "different location" banner will be displayed if the conditions are met.

Beacon activation name in the admintool

TIX2-2557 - Beacon activation name in the admintool

For organizers using the beacon activation or beacon check, you will be now able to get the following :

Name of the beacon used for activation or check in TIXNGO
Name of the beacon used for activation or check in S-360 thanks the improvement of the S-360 feedback interface. (for S-360 users)

Activation green screen security improvement

TIX2-2418 - Unique green screen per each event

During recent major events we have observed the emergence of fake apps resembling TIXNGO tickets. To enhance security and counter cheating attempts, we have introduced an enhanced green activation screen with unique and changing elements per events.

Key benefits

This enhanced security measures help mitigate the risk of fraudulent ticket replication and unauthorized access.
The unique and changing elements on the green activation screen make it significantly more challenging for cheaters to replicate and bypass the verification process.
This feature is designed to protect the integrity of ticketing operations during high-profile events, ensuring a safer and more reliable experience for attendees.

How to use it ?

Admintool Configuration

Event-level settings now include the ability to define the footer color of the green activation screen.
Organizers can specify a special animation (GIF) to be displayed on the green activation screen.

Changes in the Activation Screen

If configured, the green activation screen will reflect the defined footer color and special animation, adding uniqueness to activation for a specific event.
The feature exclusively impacts the green screens during activation and beacon checks, while leaving other screens (e.g., red, orange, blue) unchanged.

New settings per event	Greenscreen watermarked

Data export from list of tickets for data quality control

TIX2-1960 - Export additionnal data from list of tickets for data quality control

To streamline data quality control post-injection, we have introduced an enhanced bulk export feature. This feature allows for exporting all relevant details associated with injected tickets, providing comprehensive information for efficient data validation and analysis.

Name	Source
Ticket ID	existing
Ticket Image	image
Tax number	existing
Barcode	existing
Event Group Name	event.group.name
Event Group Image	event.group.image
Event Name	existing
Event Start Time	existing
Injection Date	ticketInjectionDate
Activation Group ID	activationParameters.groupId
Activation Time	Existing
Activation Method	activationParameters.method
Bluetooth Instance ID	activationParameters.instanceId
Is Activated	activated
Activated Mobile Time	New key from backend
Transfer Group ID	transferRules.groupId
Transfer Rules	transferRules (json object)
Resale Rules Group ID	resaleRules.groupId
Resale Rules	resaleRules (json object)
Latest Ticket Status Log	existing
Spectator Email	existing
Spectator Name	existing
Spectator Details	spectatorDetails
Original Spectator Email	existing
Original Spectator Name	existing
Original Spectator Details	originalSpectatorDetails
Contingent	existing
File ID	existing
Invalidation Reason	New key from backend (ticket deleted reason)
Ticket Details	existing
Extra Ticket Details	existing
Hidden Ticket Details	ticketDetails.hidden

Enhanced ticket details customization from the AdminTool

TIX2-3128 - Enhanced ticket details customization from the AdminTool

We have introduced enhancements to customize ticket details at the event level, providing organizers with greater control and flexibility.

Once enabled from the settings the new panel "Keys displayed on tickets" will be visible.
To translate the key name and/or value in other language you need to select in the top right drop-down the corresponding language.
If you want to remove a translation you added you simply can erase the content of the field and it will be back to the original value on the ticket.

Please note that when you are doing a translation and using this screen, what is happening in the backend is that the system will add a new line in reference data table (a layer above the ticket data). And every time a ticket is displayed in the app, the app will be processing both the reference data layer and original ticket data before actually displaying the info to the ticket owner. This design makes it super easy to edit ticket details with an high level of performances and let you go back to the original ticket information in no time.

Max active session reached logs

TIX2-3038 - Mobile logs when a user tries to login and is blocked due to the max active session.

A log record will be captured when a spectator reaches the maximum active session and tries to sign in on another device. The log record is now visible on the Mobile logs screen and can be searched by the spectator's email on the Support Page. These improvements provide better monitoring and support capabilities.

Improved guest details management

TIX2-2986 - Edit "My personal details" before and after a ticket check management

Currently users can edit their personal details even after a ticket has been checked (beacon check process). Based on your feedback, we have made changes to prevent spectators from editing their personal details after the beacon check as been performed.

From now, users can still access and edit their personal profile when they click on their name on the ticket. However, once a ticket has been checked and a beacon check is done, editing options for guest details are disabled. Users will be redirected to the guest details section, separate from their personal profile, where they can view the details but not make any changes.

Enhanced handling of extra information per event for ticket holders.

TIX2-2947 - "Ticket holders details required" pop up configuration

We have made improvements to the handling of extra information requirements for ticket holders based on event-level configurations.

Case 1: For wallet owners with only one event that requires extra fields, the popup for extra information is not displayed when assigning tickets. This ensures a seamless experience for wallet owners with only one event.
Case 2: Wallet owners with multiple events that require extra fields will now see the popup for extra information. However, clicking on the popup will correctly redirect to the appropriate event. When assigning tickets for event A, the extra information is required during the assignment. Once all tickets for event A are assigned, the popup for extra information will no longer be displayed, allowing for a smooth ticket assignment process for event B.
Case 3: Wallet owners with one or several events, all requiring extra fields, will continue to see the popup for extra information as before this update.
Case 4: Wallet owners with multiple events, some requiring extra fields, will see the popup for extra information. Clicking on the popup will now correctly redirect to the corresponding event. Assigning all tickets for event A will no longer require extra information during the assignment. Once only unassigned tickets for event A remain, the popup for extra information will no longer be displayed.

These enhancements ensure a more streamlined and accurate handling of extra information requirements for ticket holders across different event scenarios.

“Additional personal details required”

for the wallet owner’s details

“Ticket holders details required”

for the guests’ details

More fields on transactions screen

TIX2-2914 - new fields to transactions and export fields

Tax number, event name, and contingent have been added on the transaction screen. Note that when exporting transaction data using the Export button, the generated file also includes the tax number, event name, and contingent alongside other transaction details.

Push notifications campaigns improved filtering

TIX2-2744 - Push notifications new filters by venue & sub target group

These enhancements empower organizers to select multiple filters (event group, event site, events, and contingent) and send campaigns to targeted email recipients based on their chosen filters. This improved flexibility enables more precise and effective campaign targeting.

Enhanced multi-selection filter support for Notification Campaign Information.
Added dropdowns for event group, event site, event, and contingent selection.
Organizer can select multiple filters and send campaigns to targeted email recipients.

The following enhancements have been implemented:

Event Group: A dropdown now lists all event groups of the organizer, supporting multi-selection. The default value is set to "ALL."
Event Site: A dropdown displays all event sites of the selected event groups, also supporting multi-selection. The default value is set to "ALL."
Event: A dropdown allows the selection of up to three events from the chosen sites. The option "ALL" is not available, and the default value is empty.
Contingent: A dropdown enables multi-selection and lists all contingents associated with the selected events. The default value is set to "ALL."

TIX2-2625 - Animation around the QR Code better display

We have increased the size of the moving element on the QR code to make is more visible to the ticketing staff to ensure it's visible regardless of the light conditions.

Introducing the capability to override some settings at event level

TIX2-2242 - override some settings at event level

Added support for overriding blue ribbon display settings at event level.
Improved customization options for displaying event-specific information.

We have addressed the limitation of selecting only one field app-wide when setting up the blue ribbon display. This limitation posed challenges during events where different stadiums required displaying different information on the ribbon, depending on the event.

To overcome this problem, we have introduced a new concept called "Override settings at event level." This allows organizers to configure and modify the values for each event individually. The values are correctly exported to the mobile application, ensuring accurate display of event-specific information.

The mobile application has been updated to apply the override setting key if it exists for an event. Otherwise, it will use the setting of the application/organizer. This enables fans with tickets for multiple events to see the appropriate information on the blue ribbon and blue screen. The same functionality has been implemented for Ticket Owner Transfer Alert Keys, reflecting the event-specific override settings in the popup and ribbon.

These enhancements provide organizers with greater customization options, ensuring that event-specific information is accurately displayed to enhance the spectator experience.

Passport fields supports now a minimum of 4 characters.

TIX2-3351 The passport field available for registration and assignment supports now a minimum of 4 characters.

Spectator's App Build Number and Device ID are now available in the Mobile logs

TIX2-3191

Address line validation is now available in multiple languages

TIX2-2783 Please use crowdin key invalid_address_line

Improve back-office security and reduce account sharing by creating several admin accounts

TIX2-2170 TIXNGO back-office supports now multiple admin accounts.

While the organizer account cannot be deleted or cannot be assigned any other role, it's now possible to create other admin accounts.
These accounts will benefit from the same privileges (full access) and will be manageable by other admin users (account deletion, role change)

It’s possible to bulk edit tickets keys/values from the “Tickets bulk update” screen

TIX2-2784

Ticket Bulk Update feature allows organizers to update one key and/or value at a time for multiple tickets simultaneously. Relying on CSV, ticket update can be targeted on specific event. Back-office users have the option to apply the change on a specific ticket first and view the affected tickets count before applying the updates.

For more information on how this feature can be used, please refer to the dedicated guide Ticket Details Bulk Update

Enhanced multilingual Event Export

TIX2-3017 All the fields already available in the Event Edit Screen are now included in the Event Multilingual export.

To prevent credentials sharing and multiple login accross different devices, an organizer can define a maximum number of unique device(s) allowed by spectator

TIX2-2829 A new application setting key "Max number of devices used for one spectator account" has been introduced (default is -1 ie no limits).

After a successful login, spectator’s device counter is increased by 1. In case of logout from the device, the counter remains 1. If the spectator reaches the limit, he won’t be able to log in to the app anymore from another device. At any time, the organizer can reset the counter if the spectator reaches the limit.

Settings Export/Import between environments is now possible

TIX2-1088 In the Settings screen, logged as an ADMIN and TIXNGO_SUPPORT, you’ll see two new buttons : Export & Import

By clicking “Export” button, all the available settings (including Organizer, App, Registration & Assignment configuration and Multilingual translation) will be exported into 1 single ZIP file. In this zip file, you’ll find a dedicated CSV for each Settings family.

By clicking “Import”, you’ll be asked to upload one of the CSV files that will be validated prior to the actual import. In case of error, the import will be rolled-back to the previous working settings.

This Export/Import mechanism supports all email & push notifications communications.

It's now possible to setup different URLs for Burger Menu Item 1 and 2

TIX2-2867 Extra URL for for Burger Menu Item 1 and Item 2 (promo event)

Within Multilingual settings screen, for each language, you can define Burger Menu: Item 1 Url (key: promo.external.menu.url) and Burger Menu: Item 2 Url (promo.otherapp.menu.url)

Introduction of Silent Cancellation of Ticket Resale after the event

TIX2-1761 By default, any cancellation of a ticket resale within the S-360 system triggers a push notification to the mobile app, an effective communication tool for spectators prior to or during an event.

However, we've noticed that this feature may cause confusion when resale cancellations occur post-event, particularly while operators are tidying up the resale inventory within S-360. To avoid misleading and unecessary notifications, we've introduced a 'Post-event Silent Resale Cancellation' feature.

In order to prevent the dispatch of superfluous post-event notifications, we've implemented a new configuration key for organizers: notification.stop.after.event.expiration.days. This key allows you to define the number of days after an event during which push notifications regarding ticket resale can still be sent. By default, this period is set to 30 days. Use 0 to turn off this feature.

Visibility of Push Notifications for Deleted Tickets now tied to "showDeletedTicket" value

TIX2-3376 When a ticket is deleted (from S-360 or TIXNGO back-office), its visibility in the 'Deleted Tickets' screen and the associated push notifications will be governed by the 'showDeletedTicket' parameter.

If the 'showDeletedTicket' parameter is set to TRUE, the deleted ticket will be viewable under the 'Deleted Tickets' screen and the spectators will receive push notifications related to the ticket deletion.
Conversely, if 'showDeletedTicket' is set to FALSE, the deleted ticket will not be visible within the app. Moreover, spectators will not receive any push notifications related to the ticket's deletion.

Introducing new Mobile Logs

'No Tickets Found' during card/gate beacon ticket checks

TIX2-3355 We've implemented a new logging feature when no tickets are detected during card/gate beacon "ticket check" scans.
With this update, whenever a card/beacon ticket check fails to find tickets on the mobile, a new log mobile entry will be created 'No tickets for this match'.

'OTP Registration & Authentication'

TIX2-3317 We've made changes to our mobile logging behavior to offer more granularity in the authentication flow, specifically when using PIN Code authentication. These modifications help in distinguishing between users who've merely authenticated versus those who have completed the registration process.

For branded apps using OTP :

On successful code entry, a mobile log will be added with the action "user.authenticated"
(This mirrors the current behavior when the spectator successfully enters the PIN Code and proceeds to the registration page.)
On successful code entry and when registration is completed, a mobile log will be added with the action "user.signed-in".

For branded apps NOT using OTP :

In this scenario, only one mobile log will be generated with the action "user.signed-in"

Extended archiving duration for Communication Logs

TIX2-3447 In our ongoing efforts to enhance customer service and support, we've updated the data retention policy for our communication logs.

Instead of the previous two-month period after the event expiration date, we are now archiving these logs for an extended duration (12 months maximum).

For current, future & last 2 months past events : Communication logs will be available in the Back-Office as usual
For older past events (expiration > 2 months) : Communication logs will be archived and made available upon request to our Support team. Following the request, our team will provide a CSV extract from the database.

Control QR Code visibility after Bluetooth Beacon Activation on another phone

In connection with the setting that governs ticket transfer after Bluetooth activation (ticket.transferRules.allowTransferAfterActivationByBT = FALSE), we have introduced an additional Application setting for organizers to manage the visibility of the ticket's QR Code on a different phone : Enable QRcode hidden after first check

When you enable this feature (set to TRUE), the QR code of an activated and checked ticket won't be visible on another phone. This applies to both manual checks and checks via card. In such scenarios, spectators will see a message at the bottom of the screen saying "Ticket already checked on another phone."
This information will also be logged in the Mobile Logs. Should the ticket be activated again via Bluetooth or manually, the same message will appear within a red screen warning.

On the other hand, when this setting is disabled (set to FALSE), the QR code will be visible to users as it was previously.

Browser not supported