Table of Contents maxLevel 3
April 2, 2024
Introducing Event deletion APIs
To offer you more control and efficiency in managing your events, we developed a new set of API functionalities that will enable you to archive and delete past events and their associated content.
These new features are designed to streamline your workflow and help maintain the relevancy of your data, by removing past events and tickets data.
| Info |
|---|
In upcoming releases, ADMIN users will be able to archive & delete Events (and their tickets) directly from back-office by clicking a button in the Events list. |
Edit Event > New behaviour and UX for "Transfer Rules"
Alongside the new UI of the Edit Event screen, we generalized the new UX introduced by the "Activation Rules" to the Transfer Rules. An individual display (one row per rule) and a new 'Edit' icon have been added to provide a more intuitive and controlled way of managing transfer rules, ensuring that changes are precise and limited to the intended scope.
New mobile logs for "Max active devices reached"
We introduced a new mobile log type (user.max-devices.reached) in order to collect mobile data when max devices is reached for one spectator.
February 21, 2024
Optimization of the feedback interface
In May 2023, the "lightPayload" parameter was introduced to enhance data retrieval efficiency from the S-360 feedback interface by removing legacy status and history object from data returned to S-360.
We have taken this a step further by effectively utilizing this parameter, thereby further optimizing the volume of data returned to the feedback interface, by narrowing down to what is actually used in S-360. Currently, by setting the custom parameter additionalDiffParameters=lightPayload=true, only relevant data to S-360 will be returned to the feedback interface improving performances of both systems.
New flexibility for Mobile Features configuration in the back-office
In the past, enabling or disabling specific functionalities often required a new build of the application. This process was not only time-consuming and labor-intensive but also presented challenges in tracking which app version included specific features.
Most critically, this system did not allow for quick adjustments during live events, such as tournaments, where the ability to swiftly enable or disable features could be crucial.
To address these challenges, we've introduced new settings keys that define these mobile features :
| Location | Key | Description | Default Value |
|---|---|---|---|
| Application Settings | ticket.reminder.non-transferred | Number of minutes before sending an in-app reminder for not yet transferred tickets | 0 (disabled) |
| Application Settings | ticket.reminder.non-assigned | Number of minutes before sending an in-app reminder for not yet assigned tickets | 0 (disabled) |
| Application Features | enable-accept-reject-transfer | Enable the Accept/Reject transfer feature | TRUE |
| Application Features | enable-resale-ticket-shop-s360 | Enable the S360 ticket shop resale feature | FALSE |
Mobile logs
New mobile logs search
We've made significant enhancements to the search functionality on the Mobile Logs screen:
- Updated Search Mechanism: Back-office will now display results exclusively upon clicking the 'Search' button.
- Refined Search Parameters:
- Introduction of a 'Spectator email' search field, first implemented in the Tickets search in the previous sprint.
- Addition of 'Actions' to enable selection of specific mobile log actions.
- Conversion of 'Log level' into a dropdown menu for ease of use.
- Adoption of an 'EXACT Match' method for 'Spectator email', 'Action', 'Log level', and 'Platform', thereby improving the accuracy and relevance of search outcomes.
Previously, the grid did not prioritize information, displaying redundant or uncessary data, consequently, grid has been revamped
Layout of the grid columns has been reorganized to offer enhanced readability and relevance following a "journalistic" approach:
- 'Who' is represented by the spectator
- 'What' encompasses action, message, and log level
- 'Where' is denoted by platform, app version, and device
- 'When' is indicated by system and mobile dates.
Automatic deletion of past mobile logs
From the beginning of TIXNGO, we have consistently maintained mobile logs. As of this winter, the total has soared to 65 million logs, across all organizers.
In an effort to enhance system performance and overall stability, without compromising the business and informational value of these mobile logs, we will now retain them for a "sliding" period of 13 months before they are permanently deleted.
| Info |
|---|
If you want to preserve mobile logs for a period extending beyond the default 13 months, we strongly advise utilizing the 'Mobile logs' export feature and store the generated file into a Data-Privacy compliant space. |
Campaigns enhancements
Simplified User Interface for Campaign Creation
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.
Within "SCHEDULING OPTIONS" section, two tabs will be visible Upload CSV and Use Filters.
| Info |
|---|
Please note that these 2 modes are exclusive and nor meant to be used in combination → it's either you run your campaign using "Upload CSV" OR you "Use Filters", but not both at the same time. |
Upload CSV
Use Filters
Ticket-based filtering for notification Campaigns
Until now, our notification campaign system lacked the functionality to target specific spectator segments, particularly:
- Spectators holding more than X "transferrable" tickets for an event, who might be encouraged to transfer their extra tickets.
- Spectators possessing tickets in a specific status (Downloaded, Pending transfer, Controlled)
These limitations restricted the organizers' ability to run targeted and efficient notification campaigns.
| Status filter new options (EXACT MATCH on the selected status) | Number of "transferable" tickets |
|---|---|
|
|
Campaign's impacted spectators count
Whenever a new campaign is created or an existing one is updated, the system will now calculate the number of impacted spectators at that very moment. This count will be always visible on the Campaigns list in the column Impacted spectators.
We added an information icon in the "Impacted spectators" column. When users hover over this icon, a tooltip will appear displaying the message: “The numbers may vary between the scheduled time and the time of sending.”
Impacted spectators may vary depending on the campaign status :
| Status | Impacted spectator |
|---|---|
| SCHEDULED | Estimates based on the spectator's list at the time of campaign creation or update → displayed in italics |
| SENT | Real number of targeted spectators → displayed in plain text, not in italics |
| CANCELLED | Automatically reset to zero. This ensures accuracy in campaign records and avoids any potential confusion regarding campaign reach. |
January 16, 2024
Progressive roll-out of new Search & Export behaviour
To optimize system performance and increase user control over the search, the back-office will now load results only when the 'Search' button is clicked. This change removes the automatic loading of the initial 20 items, aligning with user preferences for more deliberate searches.
Back-Office screens UX improvements
...
Tickets List screen improvements
We have upgraded our search strategy for the Ticket List :
- New seach behaviour → back-office will now load results only when the 'Search' button is clicked.
- 'File number' and 'Spectator Email' from a 'LIKE' to an 'EXACT Match' approach, enhancing the precision and relevance of search results.
- 'Event' selection is also simplified with the merge of redundant criteria 'Event ID' and 'Event Name' into a single user-friendly dropdown list. Note: To bring more clarity, if only one event is selected, its name will be displayed.
- New 'Spectator email' search field
New search control for Spectator Email
We've implemented an intuitive improvement to the spectator email search functionality. Now, as you begin typing a user's email address, the system will automatically start searching for spectator emails that match the characters entered, beginning with just the first three characters. The more characters you type, the more refined and accurate the search results will be.
| Before typing email address | After 3 characters | With more than 3 characters |
|---|---|---|
|
|
|
| Info | ||
|---|---|---|
| ||
This new search behaviour will is first be available in the Ticket list. Other screens will be updated accordingly later. |
...
Events screen improvements
We slighly adapted the Search Critierias available in the Events screen by :
- merging the redundant criteria 'Event ID' and 'Event Name' into a single user-friendly dropdown list.
- increasing the size of both Event and Event Group fields
Edit Event > New behaviour and UX for "Activation Rules"
A new 'Edit' icon has been added for activation rules, to provide a more intuitive and controlled way of managing activation rules, ensuring that changes are precise and limited to the intended scope.
It enhances the overall efficiency of ticket management and reduces the risk of unintended modifications.
Simply click on this icon to modify an existing activation rule.
- Save Functionality: Upon clicking 'Save' after editing, the system will selectively update only those tickets that are linked to the modified activation rule. This targeted update ensures that changes are applied exclusively to the relevant activation rule without affecting other elements.
- Cancel Functionality: If you decide not to proceed with the changes, clicking 'Cancel' will leave both the activation rule and the associated tickets unaffected. This feature provides a safe way to explore modifications without committing to them immediately.
| Info | ||
|---|---|---|
| ||
As part of our strategy to enhance Event Management, we will be making corresponding adjustments to the Transfer Rules in the forthcoming ZUMV1 sprints |
New search critierias in Campaigns screen
In our continuous effort to enhance back-office user experience and increase adoption, we are glad to introduce new search critierias within Campaigns list screen.
New 'Status' Dropdown: Expanding Search Capabilities
We have introduced a new "Status" dropdown, broadening the scope of search capabilities for our users. This feature includes several options to cater to diverse user needs:
- All (excl. cancelled): Set as the default option, this allows users to view all active and planned campaigns, excluding those that are cancelled. It provides a streamlined and focused view of current campaign activities.
- Scheduled: This option is designed for users who wish to view campaigns that are scheduled for future deployment.
- Sent: Users can now filter and view campaigns that have already been dispatched, offering insights into past activities.
- Cancelled: This addition makes it easier for users to search for and analyze any campaigns that have been cancelled.
- All: Offering a comprehensive overview, this option enables users to view campaigns across all statuses.
Fine Tuning of the 'Language' Dropdown
In line with these improvements, we have also fine-tuned the "Language" dropdown. This update involves a change in the title to make it clearer and more intuitive for our organizers. The revised title aims to provide a better understanding and facilitate easier navigation in selecting the campaign language.
December 13, 2023
Configure the available gender options from the Registration settings
In today's diverse world, inclusivity and respect for personal identity in data collection are not just ethical imperatives but essential components of effective and responsible practices.
We have now introduce the ability to select two new additional values (Other, Prefer not to say) that can be collected for Spectator's gender.
To do so, go the Registration settings and look for Available gender options (setting key: profile.display.gender.options) and select the additional options that suit your need and click Apply
Crowdin translation keys
- Other: gender_others_label
- Prefer not to say: gender_prefer_not_to_say_label
...