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.

Support Page

Tickets in "Transfer Pending" Status are now visible in the Support Page

Organizers can now easily locate and view the tickets of the sender or the recipient directly from the Support page screen.

As of now, spectator's tickets are shown in the Tickets section.

A new entry dedicated for "Pending transfers" is now available in the drop-down list.

If you select "Pending transfers" the grid will contained a refined and tailored view of all the tickets in Pending transfer status associated to this spectator, no matter if it's an outgoing or an outcoming transfer.

Tickets

Export tickets contains now the last active time of the spectator

In case you updated an event, it's essential to establish whether spectators were online to obtain the refreshed data, enforcing the security of an event. We have now included the Last Active Time in the Tickets export CSV file.

After updating an event, we advise to extract event's ticket using the 'Export Tickets' function. Subsequently, analyze the 'Last Active Time' to determine the extent of spectators' tickets that remain unupdated.

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

Ticket status history now reflects the genuine controlled time from the Access Control System in the additional information column, while the system date contains the date and time when the Controlled status was processed by TIXNGO.

Ticket check secondary activation informations are now sent to S-360

To better cater to the evolving needs of both S-360 & TIXNGO systems, and in alignment with the primary and secondary activation capabilities, we've updated the feedback interface.

• If a ticket is activated using a primary method (ONLINE, OFFLINE, BEACON), as before, the feedback interface will return the primary (and only) activation details such as type, phone model, beacon, activation date.
• If a ticket is activated using a primary method and then checked with the Ticket Check feature, the feedback interface will now return the specifics of this check, including the latest activation type, phone model, beacon, activation date. In this case, primary activation details will be superseded by secondary activation details.

Spectators

Search spectators by app version and browse spectator devices

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.

Mobile logs

Mobile logs now includes System & Mobile time

To streamline troubleshooting and mitigate potential misunderstandings, mobile logs have been enhanced to encompass both System and Mobile time.

Note: In the Mobile logs export CSV file, both date will be included.

Screenshots & Screen recording are now recorded in the mobile logs

To provide better monitoring & support capabilities during high-attendance events, regardless of whether the 'Protect screenshot and screen recording' feature is enabled or disabled, a log record will be captured when :

• When an user take a screenshot on the ticket app, organizers can see a record of log with the action user.screenshot.taken
• When an user record a video on the ticket app, organizers can see a record of log with the action user.screen.recorded

As always, these two new recorded actions will be visible on the Mobile logs screen and can be searched by the spectator's email on the Support Page.

Known Limitations:

• If spectators start recording before they open the app, the app cannot detect the recording and therefore cannot log the action.
• For Android devices :
  • Spectators cannot take and record video log when screen protection is TRUE
  • The way to detect screenshot action is by checking whether a new image that contains the word "screenshot" in the name is created. Therefore, the app needs permission to read the storage/media in order to work.