Table of contents
- Big bangs
- Cool new features
- Small new features
- Feedback Interface Performances Improvements
- Bigger font size of number of tickets on the green screen
- make sure we can't change the activation time of already activated tickets
- Wallet user app language in the admintool
- Tickets in different location yellow banner
- Beacon activation name in the admintool
- Data export from list of tickets for data quality control
- Max active session reached logs
- Improved guest details management
- More fields on transactions screen
- QR code animation more visible
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, ....) 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. 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.
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 :
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
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.
These enhancements ensure a more streamlined and accurate handling of extra information requirements for ticket holders across different event scenarios.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
The following enhancements have been implemented:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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
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.
|
