Table of contents
...
| Product features | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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, ....)
Less is better, preparing the Feedback interface "summer body" by removing the ticket details that are not used in S-360.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Internal - Cleaning the push notifications TIX2-2927 - Cleaning the push notifications for invalidation reason: "not cancelled" from the TIXNGO console The S-360 and TIXNGO integration now ensures that when a ticket is cancelled in S-360, the cancellation is also reflected in TIXNGO. To enhance user-friendliness, an in-app notification is triggered before the cancelled ticket disappears from the wallet. The notification is based on the selected cancellation cause in S-360 and can be configured in the TIXNGO back-office. However, there is an issue with the current implementation. There are numerous cancellation causes, and administrators/organizers can define the notification text for each cause. One of the causes called "NOT_CANCELLED" is the default value in S-360, indicating that a ticket is "not cancelled" regardless of its printing status. Strangely, S-360 does not allow operators to select this cause when cancelling a ticket, creating confusion and concern for customers. To address this, we now prevent the customization of notification texts for unsupported and unnecessary cancellation causes, thereby simplifying the system and avoiding customer confusion. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
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 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 :
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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
How to use it ? Admintool Configuration
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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
