/
Introduction to V4 Event semantics

Introduction to V4 Event semantics

What are event semantics?

In addition to the ticket design rules where the layout can be selected and configured, TIXNGO also leverages event semantics to customize the mobile tickets.

image-20241205-103928.png
The ticket design rule still controls the layout and it’s configuration: colors & images to use

It’s important to understand that event semantics are optional but when defined, will modify the event list and ticket detail screen independently of the ticket layout chosen in the ticket design rule.

Event semantics are defined at the event-level and can be easily modified in the event edition screen in BackOffice, under the Details tab. The available event semantics depend on the event type. By default, all events are of type STANDARD, meaning they have no specific event semantics.

image-20250624-144722.png
Event type selection in the Event detail & Event Schedule configuration

Currently, event semantics are stored in practice as event metadata. If they can be defined using the backoffice, they can also be directly injected at event creation from S-360 by setting a variable like event.metadata.n.key & event.metadata.n.value.

The event type for instance can be injected by setting the following variables in the injection template:

  • event.metadata.n.key = "event_type"

  • event.metadata.n.value = "STANDARD" or any other supported type

Where n is the position of the metadata in the list (must be unique integer, starting with 1)

Common semantics

Some semantics are applicable regardless of the event type and their configuration is thus always visible.

Event schedule

The different times of the event schedule that will be displayed in the ticket detail screen (see V4 Ticket Layout > Classic for instance) are event semantics that can be configured in the following way:

  • Choose to display or not the line

  • Define the corresponding time (hour & minutes)

image-20250624-151949.png
Event schedule time example

Note that the labels actually displayed to the user can be configured in crowd-in under the following code:

  • event_gate_opening

  • event_ceremony

  • event_start_time

  • event_gate_closing

and event_time_schedule for the section title

Event time schedules is stored as a stringified JSON array in the event_time_schedule metadata. It is NOT recommended to set it in the injection template in S-360 to avoid mistakes. Please configure this directly in backoffice after ticket injection (it can be modified at anytime and will be automatically update on ticket if mobile app is online).

Here is an example if needed: "[{\"time\": \"16:00\", \"label\": \"event_gate_opening\"}, {\"time\": \"20:00\", \"label\": \"event_start_time\"}, {\"time\": \"23:00\", \"label\": \"event_gate_closing\"}]"

Specific semantics behavior

Please refer to the pages below for additional information on the event semantics available for each event type and how they are leveraged by TIXNGO mobile application.

© TIXNGO 2023 - Lo