V4 Ticket Layout > Custom Flow
Why should you use it?
This feature will support organizer that may not use the
How does it work?
A new concept of Custom flow which is used only on the ticket detail screen in the “boxes” to guide users in their journey onsite with full flexibility.
Tickets injected to TIXNGO can define a navigation flow with full freedom in S-360 injection template.
Injected by S360
User can define the flow in the Integration Template when injecting tickets to TIXNGO by setting the variable
TicketDetail.flowFormat:
ticketDetails.flow.$index$.[key|value] = ‘Z1’Example:
ticketDetails.flow.1.key = 'Zone' ticketDetails.flow.1.value = 'Z1'
Injected by csv to TIXNGO
User can use this template to define the navigation flow in the column of ticketDetails.flow
Example:
Column title: ticketDetails.flow
Value: [{"key":"Room","value":"E1"},{"key":"Door","value":"E1"},{"key":"Zone","value":"Z1"},,{"key":"Floor","value":"F1"},{"key":"Column","value":"C1"},{"key":"Seat","value":"S1"}]
This flow will be visible only in the ticket details on Mobile and Ticket support on Backoffice
=> The seating details are still displayed everywhere else as they are meant to uniquely identify the access given by the ticket and in particular:
on all mobile screens except the ticket detail: transfers, deleted tickets;
in All notifications & email communications.
Seating details will still be passed automatically and stored separately on the ticket so it can be used for all filtering & searching in Backoffice and other special features (like warnings when tickets with different gates are kept on a same wallet for instance).
The labels & values will be displayed exactly like injected, without any translation and in the order provided.
NOTES:
This is the display priority used by the Mobile app:
If Custom Flow is present, the Mobile will display the Custom Flow
If there are no Custom Flow, display the Seating Details (Introduction to V4 Design rules - TIXNGO Public Documentation - SECUTIX Documentation)
© TIXNGO 2023 - Login