2025 Rimpfischhorn V4

2025 Rimpfischhorn V4

Objectives & high level scope

The objectives of this release are:

  • finalize the Spectator V4 refactoring and rationalization, only for customer using SSO;

  • push furthe

  • start decommissioning ticket V3

Migration to tickets V4 will be complete by end of this version and we immediately start decommissioning ticket V3 code and now useless historical data to reduce our operational costs.

Spectator V4 refactoring

Full refactoring of spectator-centric data management, focused on the SSO-only future

We modern

New and improved mobile devices & sessions management

We rebuilt spectator devices and sessions management as well to improve performance while maintaining our strong focus on security and control.

New reporting domain for spectators & their devices

Following the V4 design, all data of spectators & their devices are published in a dedicated reporting domain to empower organizer to leverage those data without impacting the operational system.

Tickets V4 improvements

Clarify ticket statuses & history

Are you puzzled by the new ticket statuses? We adjusted them to clarify and simplify the ticket history and align better with what syncs to S-360. Troubleshooting and spectator support, especially in complex cases, will benefit from these improvements.

Better support venues specificities in seating details flow

Does your complex venue signage not fit the S-360 physical configuration? First, you can configure seating detail labels in the Ticket Design rule.

Need more flexibility? Second, define a custom flow to display on the ticket screen using the S-360 injection template when the physical configuration can't model the venue signage.

Full bulk ticket update

Need to rename a gate or fix a typo in your TIXNGO tickets? We are bringing back the ability to bulk edit seating details and ticket metadata directly from the TIXNGO Backoffice screen!

Better support spectators with lots of tickets & transfers

Managing spectators with dozens, hundreds, or thousands of tickets for multiple competition events? We enhanced the Backoffice spectator support screen with filters and searches to help operators handle these spectators more efficiently.

Other Miscellaneous improvements

We plan a list of small yet impactful improvements to the mobile app and Backoffice UX that will simplify everyone's work. Follow the detailed release notes to find these hidden gems.

Release planning

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

 

European slots (5)

American slots (25 & 26)

PRE-PROD

PROD

PRE-PROD

PROD

RIMV4.1

29.10.2025

04.11.2025

29.10.2025

04.11.2025

RIMV4.2

12.11.2025

18.11.2025

12.11.2025

18.11.2025

RIMV4.3

26.11.2025

02.12.2025

26.11.2025

02.12.2025

RIMV4.4

10.12.2025

16.12.2025

10.12.2025

16.12.2025

RIMV4.5

24.12.2025

30.12.2025

24.12.2025

30.12.2025

RIMV4.6

07.01.2026

13.01.2026

07.01.2026

13.01.2026

Detailed release notes

Here will be unveiled, one increment at a time, the new features available in the next deployment.

RIMV4.3

Better support spectators with lots of tickets & transfers

Managing spectators with dozens, hundreds, or thousands of tickets for multiple competition events? We enhanced the Backoffice spectator support screen with filters and searches to help operators handle these spectators more efficiently.

image-20251127-081316.png
New powerful filters in the Past transfers view in the Spectator Support Screen

More details in https://go.confluence.secutix.com/wiki/x/UwiqCw

Miscellaneous small changes

In the Communications screen, it’s now possible again to list ALL communications sent over a given time period, no other filters required.

Before scheduling a new Notification Campaign, a confirmation is now required. This confirmation popup includes the number of spectator that this campaign will reach.

RIMV4.2

Better support venues specificities in seating details flow - part 2

Need more flexibility that seating details label overrides? Define a fully custom flow to display on the ticket screen using the S-360 injection template when the physical configuration can't model the venue signage.

image-20251113-074956.png
Custom flow defined for a ticket, visible in BackOffice & on the Mobile app

More details in V4 Ticket Layout > Custom Flow

Clarify ticket statuses & history

Are you puzzled by the new ticket statuses? We adjusted them to clarify and simplify the ticket history and align better with what syncs to S-360. Troubleshooting and spectator support, especially in complex cases, will benefit from these improvements.

Smarter Logs & History

image-20251112-104327.png
New Ticket History Overview simplified screen, matching 1:1 the history synchronized with S-360

Mobile Timestamps: Ticket status logs now include the mobile device’s timestamp, providing precise context for every event—even offline or manual activations.

Ticket History Redesign: The “Status history” section is now “Ticket history,” split into two tabs:

  • Overview: Major events at a glance, matching the S-360 summary & using S-360 mobile statuses terminology.

  • Detailed: All the granular details, with improved columns and clearer timestamps.

More information in V4 Ticket Support screen

More accurate ticket deletion tracking

image-20251112-110608.png
A ticket in DELETION PENDING status

Introducing the DELETION PENDING status! Now, whenever a ticket deletion is requested (via S-360, API, or Backoffice), you’ll see this new status until all devices confirm deletion. If the ticket isn’t present on any device, it jumps straight to DELETED.

The DELETION_PENDING status is visible everywhere you need it: main ticket lists (with filtering!), spectator support screens, ticket support screens, and more.

This change brings us back in line with S-360, making troubleshooting easier and statistics clearer.

Enhanced Ticket Attributes

  • Delivered Attribute: A new “Delivered” attribute added (with a timestamp!) to record the very first time a ticket is downloaded. This attribute never resets, ensuring you always know when a ticket was first delivered, regardless of the number of times it has been transferred.

  • Activated Attribute: Now, the “Activated” timestamp is only reset on manual deactivation, deletion, or specific transfe

  • Comprehensive Filtering: You can now filter ticket lists by Delivered, Assigned, and Kept by Owner attributes, making it easier than ever to find exactly the tickets you need.

S-360 Feedback Alignment

Statuses in the feedback interface are now fully aligned with S-360. We also improved the additional info field, including for instance recipient email visibility for pending transfers. More information in S-360 <-> TIXNGO V4 Interface.

Other changes

In the ticket list screen, it is now possible to filter tickets by Contingent. Please note that the Contingent filter is available only after selecting at least one event.

RIMV4.1

Better support venues specificities in seating details flow - part 1

Does your complex venue signage not fit the S-360 physical configuration? You can override seating detail labels in the Ticket Design rule.

Want to hide some seating details in some cases? The Ticket Design rule now let you configure the visibility of ALL fields.

More information: Introduction to V4 Design rules | Ticket fields visibility customization

Full custom flow is around the corner, we just need to wait for TIXNGO interface on S-360 to be adapted.

Other changes

Mobile

Returning a ticket, or transferring it from Backoffice, will not require acceptance anymore, even if transfer accept/reject feature is enabled. More information: TRANSFER ACCEPTANCE

It will also be possible to show only some of the deleted tickets in the mobile app depending on the deletion reason. More information: DELETED TICKETS VISIBILITY

General performance enhancements have been implemented, especially for spectators having lots of tickets.

 

 

© TIXNGO 2023 - Login