Release Scope

TIXNGO V4

• V4 Reporting domains including Tickets, Transfers, Status statistics

• Reminders emails

• V4-compatible Spectator Account deletion

Back-Office

• V4 Tickets: CSV injection, Soft-deletion, Bulk update, Initiate transfer

• V4 Spectator Support screen > Previously Owned tickets

• V4 Configuration: Import/export rules

• V4 Communication Logs

Mobile

• New ticket design for Matches (Team VS Team)

• V4 compatible deleted items & resale screens

Mobile R&D

• V3 ONLY - Proof of Concept for Ticket Check leveraging NFC technology

Release planning

Here are the planned installation dates of every iteration of this version.

Detailed Release Notes

RIMV2.6

Reporting domain

We are thrilled to introduce in this version a our first reporting domains empowering organizers to access historical statistics or business data directly without impacting the operations.

In this release, the following first reporting endpoints are published:

• Event statistics: where the global ticket statistics (downloaded, transferred, controlled, …) are available.

• Monthly injection reports: used to follow the ticket injections over time

• Event ticket ownership report: extract the tickets list with all up-to-date information (status, current owner, …)

Full detailed documentation: https://go.confluence.secutix.com/wiki/x/pQYFDg

Show tickets previously owned by spectator

Ever needed to support a spectator having transferred a ticket in the past? Now all the past transfers (outgoing or incoming) will be easily available right from the ticket support screen.

Open

Past transfer history for a given spectator

This is a full history of all the tickets that have been owned at some point by the spectator, nicely ordered by descending transfer date meaning the latest transfers are displayed on top. From this list you can easily continue your investigations by opening a specific ticket or other spectator using the link (use middle button click to open in a new tab).

Bugs fixed

RIMV2.5

This is a consolidation release where the team focused on finalizing, hardening and fine tuning RIMV2 new features. And now some long-awaited features are ready to be widely used!

New Match design!

This is probably the feature with the highest added value in RIM V2 for our sports organizers! In order to fully leverage the power and simplicity of V4 centralized ticket design rules and still have different and appealing visuals for every match, we are excited to introduce a native.

Open

Your event is a match between 2 teams? Make your event card & tickets looks like this with only a simple configuration on your event! And yes, the screen is automatically alternating between the teams & competition logo if defined

More importantly, this is achieved through defining what we call event semantics: detailed business information depending on the event type. This is paving the way for future tailored designs and with the new V4 design rules, for professionally designed tickets with a simpler than ever configuration! Learn more about event semantics here Introduction to V4 Event semantics, and match events here Event semantics - Match

Override design rules at event-level

The V4 design rules allows organizer to simplify and rationalize the configuration of how ticket should be displayed in the mobile app. However sometimes, some images or colors should be different for some event (like the sitemap for away matches for instance).

From this release, there is no more need to multiply your design rule for small changes. You can simply override some elements of the design rules in the event edition screen in Backoffice:

Open

Ticket design customization tab in Event edition screen

More information: V4 Ticket Layout - Overriding at event-level

Other changes

• It’s now possible to export the full ticket configuration from an environment. A bit of patience and in the next release the import will be there too to greatly simplify onboarding and testing in pre-production new configuration! More information on this here: Introduction to Ticket Configuration V4 | Export/import of rules

• Reminder emails are now sent to recipients who have not registered for their injected or transfer V4 tickets. A new organizer configuration key allows to limit the total number of reminder sent to a given spectator: email.reminder.limit.max-number.spectator (default 4)

• Technical Progress continues on the reporting domain with computation of ticket details.

RIMV2.4

Ticket injection through CSV, V4-ized

CSV injection ticket is back, with the new ticket V4 model, and simplified UX.

Open

New CSV ticket injection screen

Download the new template, fill it then upload and submit the file → done! Please refer to the CSV Injection for more details.

Update ticket v4 data from Backoffice

From the ticket v4 support screen it’s now possible to change for a given ticket:

• the ticket rule applicable (with preview of the current & new rule), except the Activation rule to avoid any operational impact;

• the ticket metadata (main, extract, hidden);

• reset the transfer counter to 0.

Open

Ticket support screen in Backoffice with update buttons

Later in this release, the ticket rule will also be updatable in bulk.

Ticket deletion from backoffice

You can now delete a ticket from a spectator wallet directly from Backoffice. Select the reason in the dropdown and the spectator will be notified using the corresponding message configured in the communication templates.

Open

Ticket delete action & popup screen from Backoffice

Other changes

• Technical Progress continues on the reporting domain with computation of Transfers, Activation, and Status statistics.

RIMV2.3

Transfer ticket from Backoffice

Need to transfer a ticket from spectator A to B but spectator A is unable to do it for some reason? Just open the ticket support screen and click on the transfer button!

Open

Ticket transfer screen from Backoffice

This will initiate the standard transfer process, and the status log will clearly indicate this has been triggered from backoffice (and by whom):

Open

Ticket status log showing a pending transfer initiated from Backoffice

Other changes

• Ability to keep a ticket for oneself is now again available in ticket v4. Ticket kept by owner are flagged and a star is visible in the app:

• Confirmation email is sent with a unique, time-limited link to the spectator when account deletion is requested and future tickets are sti

• Compliance Anonymization logic is now adapted to ticket v4 data to comply with data privacy requirements.

RIMV2.2

Grouping of injection notification emails

Injection notification emails are now grouped and sent only once per hour and per spectator, with the list of all tickets received. See https://go.confluence.secutix.com/wiki/x/VgDeCg for more details.

Other changes

• Ticket transfer level is now computed on theUsage Rule configured for this ticket (see https://go.confluence.secutix.com/wiki/x/IQf_Bw for more details). This allows taking into account any configuration change at any time.

• Technical In this release, progress has been made on the reporting domain by exposing the first endpoints.

• Technical Pin code authentication emails are now sent through new v4 communication engine.

RIMV2.1

V4 Push campaigns

Finalization of Back-Office screens. New push campaign can now be created and modified from the backoffice. See Introduction to V4 Campaigns & https://go.confluence.secutix.com/wiki/x/BIBlD.

V4 Communication Logs

Communication logs are now available, from the main menu to search globally (filters criteria are now mandatory) as well as directly from the spectator support screen. Find more about this in Introduction to V4 Communications Logs

Other change

• Technical Preparing the database model for Ticket, Ticket Holder and statistics reporting domains.

Bugs fixed