Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
Zumstein V2 Release Notes Highlights
VIEW FULL LIST
Click here
Back-office
Searching the Spectators list is now configured to perform an 'EXACT Match' for 'Spectator email', thereby improving the accuracy and performances of the search.
Standardizing mobile logs about Spectator
A new naming convention has been applied to "Spectator" mobile logs action and message.
Collecting & categorizing Spectators origin
TIXNGO now collects and categorizes the origin of each spectator (registration, ticket injection, ticket transfer,...)
Campaign enhancements
We're enhancing the user interface to clearly differentiate between CSV-based and manual campaigns. This simplification will streamline the campaign creation process, making it more intuitive and efficient for organizers.
Transaction Logs screen removal
In our ongoing efforts to tidy up the back-office, we've removed the transaction logs menu entry and screen, following the successful removal of the blockchain earlier this year.
t's now possible to benefit from the enhanced Downloads experience for Spectators export.
Event Ticket Ownership report includes Spectator's address
Event Ticket Ownership report has been updated in order to contain spectator's address
Mobile logs for beacon activations now contains beacon name in the message
Mobile
We have identified an issue where the "cross" icon on pop-ups is misleading, causing users to mistakenly believe it will close the pop-up. To prevent misunderstandings and enhance user experience, we have updated the icon.
Messages display in the Tickets to Download screen aesthetics and usability has been improved both to better align with our new UI design.
Enhanced Profile Management within the mobile wallet
We released a significant update of the "Edit Profile" screen, addressing the management of mandatory and optional fields to enhance user experience and ensure compliance with data protection regulations.
In 2023, we introduced a feature allowing spectators to request and use a registration code up to five times (see Release Notes article here).
This mechanism has now been extended to include an exponential delay if the registration code is requested more than five times, to prevent excessive or unreasonable requests.
When the email checker identified a unusual e-mail address, the warning message appeared briefly and could be easily ignored by the wallet owner. In addition to improving the visibility of notification messages, we've implemented an extra step (i.e. a pop-up) to ensure that users with wallets are actively engaging with these messages.
Redesign of the "Deleted tickets" screen
As we introduced a new UX for our mobile wallet, we continued modernizing existing screens. In this release, we followed the same approach and improve the "Deleted tickets" screen.
Streamlining the order of menu entries
