Events

Default time for time-based activation methods

Previously, when an organizer used offline activation for a ticket but did not set an activation time in the template used for injection, no activation time was set, and the ticket did not get activated.

With this release, if an activation time is not set during injection, a default time will automatically be applied to ensure the ticket gets activated based on the value of the setting Default time for time-based activation methods, x hours before event start time (key ticket.activation.delay). By default, the delay is set to 3 hours.

Furthermore, for all time-based activation methods, the activation time can be overriden in the Edit Event screen within Activation section.

Image Added

Tickets

Export tickets contains now the last active time of the spectator

...

Note: In the Tickets export CSV file, the column Last Active Time will be available and placed right after the Contingent column.

Improved display of Controlled date in Ticket Status History

...

Search spectators by app version and browse spectator's device(s) list

By using the App Version filter, you can now retrieve the list of spectators, who have at least one device, in the provided app version.

In the column labeled 'N.B DEVICES ACTIVE (TOTAL)' you will observe the quantity of active devices associated with each spectator.
As indicated by the column's title, the initial figure represents the number of currently active devices, while the number in parentheses signifies the total devices that have been utilized at least once by the spectator.

For an individual spectator, upon clicking the device count, a popup will display a comprehensive list of associated devices, including device name, app version, platform, os version, device id and last sync time.

Note: In the Spectators export CSV file, the column App Version will be also available and placed right after the App Language column. App Version column will contain a JSON representation of the table displayed in the popup.

...