Objectives & high level scope

V4 refactoring

• Tickets V4 improved based on the rollout feedbacks. In particular: simplify ticket rules injection & easily define what fields are visible on the ticket.

• Spectator V4 base refactoring with SSO support

• Spectator V4 mobile devices & sessions management

Release planning

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

Detailed release notes

RIMV3.6

Ticket rules bulk update

You injected tickets and find out that an important number of them should use a different design/usage/data collection rule ? No need to reprint from S-360, you can now directly fix those tickets, in bulk, directly from TIXNGO backoffice!

Open

New bulk update screen with filters and rule selection to update

More information: https://go.confluence.secutix.com/wiki/x/dgAXEw

Fixing small issues on the ticket display

Open

Classic ticket example with new square team logos, long team name and new badge background color.

• We removed the round cropping on the team logos when using Match event semantics. So logos can use the whole space available in the layout and in particular logos with special shapes can be better displayed without reducing their size (see https://go.confluence.secutix.com/wiki/x/hAAjDw).

• Long team names are now always displayed completely (abbreviate them if you want).

• Background color of the badges (match number, accessibility icon, wristband icon) have now same colors as the seating details background (and other action icons). If desired, the color can be customized separately in the app theme.

• On curiosity layout, long event names of more that one line are now aligned with the sections below (we added margins).

Improve tracking of ticket deletion on devices

From now on, a dedicated Ticket status log entry will be recorded upon ticket deletion confirmation by every device having downloaded it. This will bring more clarity until we go even further and bring back the Deletion pending status in RIMV4.

Open

Example of a ticket deleted from Backoffice with following confirmation from 2 devices

Other changes

• During ticket injection, TIXNGO will now refuse any ticket with missing ticket rules (all rules), or referencing a ticket rule name that doesn’t exists for the organizer. If you suddenly start encountering errors in TIXNGO injection interface, it means that your rule mapping is incorrect in your injection template.

Bugs fixed

RIMV3.5

Most of this release is about making progress on spectator V4.

Bugs fixed

RIMV3.4

This release is mostly technical, making progress on the spectator v4 refactoring.

Bugs fixed

RIMV3.3

Event statistics in Backoffice

As following event statistics is one of the most common reporting needs, we introduce a dedicated backoffice screen to simply access the corresponding reporting domain.

Open

Event statistics screen from backoffice

More information here: https://go.confluence.secutix.com/wiki/x/egAWEQ

Other changes

• Tickets rules referenced in ticket injection are now automatically linked to the event. It is thus not required anymore to link them manually in BackOffice before injecting (or putting all rules as “used by default” for new events).

• When a spectators returns a ticket to its previous owner, the recipient cannot be edited from the Transfer center anymore.

Bugs fixed

RIMV3.2

This release is mostly technical, making progress on the spectator v4 refactoring.

Bugs fixed

RIMV3.1

Added flexibility on ticket fields visibility

The design rule now allows defining which fields should be displayed on the ticket (if they are provided during injection, of course):

Open

Select the fields to display on a ticket at the design rule level

More details here:Introduction to V4 Design rules | Ticket fields visibility customizationPreview

Also, it is now possible to add custom fields value in the first section of the ticket using the main ticket metadata (in the CLASSIC layout only):

Open

Ticket main metadata displayed in the first section of the ticket

See also V4 Ticket Layout > Classic | Ticket metadata displayPreview

Other changes

• It’s now possible to import to an environment tickets configuration exported from another environment. Onboarding and testing in pre-production new configuration should now be much simpler! More information on this here: Introduction to Ticket Configuration V4 | Export/import of rulesPreview

Bugs fixed