List of available Settings

Standard TIXNGO proccess (STP) or Manage by Organizer (MBO)

If STP, then the deletion is applied with TIXNGO normal process

If MBO, users is redirected to organizer's URL (configured on Crowdin)

Values: (with X, Y, Z are Integers and X is required)

Latest version of the app that requires user to install. (Should always same or later than minimal one)

There are no features implemented yet related to this one. An example of a potential feature, you might be interested and asked us to develop, would be a new feature to display a pop-up in the app informing a new version is available

Values: (with X, Y, Z are Integers and X is required)

Oldest version of the app that requires user to install. 

Using for force update purpose: the organizer can decide to request to have a minimal version of the TIXNGO wallet to be used. So the app will show you a informative screen to ask you to update the app (cannot do anything else in the app).

Burger Menu: Item 1 Visibility

Values: ACTIVE, INACTIVE; control whether the link to external website is shown in the menu. Order of the link in the burger menu is fixed.

promo.external.menu.displayed

Event List: Promo 2 Position

Values: INACTIVE, TOP, AFTER_FIRST, BOTTOM; controls where the other app link box is shown in the event list view of the app.

promo.otherapp.event.position

Event List: Promo 2 Image URL

Link of the image that will be displayed in the box related to the otherapp

promo.otherapp.image

Burger Menu: Item 2 Visibility

Values: ACTIVE, INACTIVE; control whether the link to another app is shown in the menu. Order of the link in the burger menu is fixed.

promo.otherapp.menu.displayed

Protect screenshot and screen recording - Secret code to change in-app

If you need to disable protection against screenshots and screen recordings per device, follow the steps:

Step 1: Triple tap on the bottom of the menu (where all details about the app are displayed).
Step 2: Provide a support code on the next screen.

Important notes:
Login out/in keeps the setting. Reinstalling the app removes the setting.

screen.protect.shot.record.secret-code

Enable online/offline check if device reached max active sessions

Values: true/false; enable/disable the online check if device readed max active sesssions.

(For login restriction security purpose)

security.session.enable-online-check

Max number of active devices at once (only if security is enabled)

Values: Integer >0
(For login restriction security purpose)

security.session.max-active-phone

Values: FALSE, TRUE; disable or enable the allowing only one session. 

(For login restriction security purpose)

There are no differences between “Only one active wallet session is allowed” and “Max number of active devices at once (only if security is enabled)” = 1.
It would implies the same behavior. The first one was the first to be implemented. The second one at a later stage.

Values: Integer ≥ 0
If the Emergency offline activation feature is enabled, at the configuration time, if ticket is not activated, then activate the ticket offline

Number of minutes before sending a non-assigned reminder in the app

Values: Integer > 0
Pop-up message in app for assigning ticket reminder (F.). Value indicates the interval between 2 pop-ups.

ticket.non-assigned.reminder

the pop-up & yellow ribbon asking for transferring/assigning tickets will be displayed

true: need to check if the spectator has more than 1 transferable ticket and at least one of them is unassigned
false: only need to check if the spectator has more than 1 transferable ticket

the pop-up & yellow ribbon asking for transferring/assigning tickets will be displayed the first time, X (hours) before event start time

Number of minutes before sending a non-transferred reminder in the app

Values: Integer > 0 ,
Pop-up message in app for transferring ticket reminder (RBL). Value indicates the interval between 2 pop-ups. 

ticket.non-transferred.reminder

Number of hours before event start time sending different-gates/blocks first message in the app

Values: Integer > 0

Pop-up message in app for transferring ticket reminder. 
Value indicates the number of hours between 1st pop-up and event start time. 

(Dependent with  ticket.owner.transfer.alerts and ticket.owner.transfer.alerts-keys )

In case you have tickets for different block/gates. This is for pop-up message. Organizer need to enable and define these keys to be able to use this feature:

·        ticket.owner.transfer.alerts (enable the feature on mobile)

·        ticket.owner.transfer.alerts-keys (Define the key to compare)

ticket.owner.transfer.alert.hour

Number of minutes before sending different-gates/blocks reminder in the app

Values: Integer > 0

Pop-up message in app for different-gates/blocks reminder , value indicates the interval between 2 pop-ups. Number of minutes before sending different-gates/blocks reminder in the app

·        In case you have tickets for different block/gates. This is pop-up message. Indicates the interval between 2 pop-ups.

·        Same as above, organizer need to enable and define these keys to be able to use the feature:

·        ticket.owner.transfer.alerts (enable the feature on mobile)

·        ticket.owner.transfer.alerts-keys (Define the key to compare)

·        ticket.owner.transfer.alert.hour (Define the first pop-up time)

ticket.owner.transfer.alert.interval

Ticket Owner Transfer Alert Keys

Values: List of ticket details main or extra key  which define by organizer (eg. Gate, Block, Row, Seat,...) which is used to notify ticket owner transfer tickets

(Dependent with ticket.owner.transfer.alerts feature and ticket.owner.transfer.alert.hour )

ticket.owner.transfer.alerts-keys

Values: Integer >= -1 (-1 means no limits)
Organizer can define a number of unique devices to be used to login for one account

Values: Integer >= 0 (0 to turn off the feature)

After 48 hours or today is on match day and the recipient hasn't download the tickets yet, display the below popup, it will repeat after each value of the given number in minutes

Currently, TIXNGO is supporting 3 login mode on mobile ticket apps
COGNITO_STANDARD
COGNITO_PINCODE
OIDC

Values: true/false

Anonymize ticket holder information after x days the event ends (set 0 to turn OFF the feature)

Value: Integer (days)(count from event end-time)
Default value = 0 → OFF feature
If current time is X days after event end-time, ticket holder information will be anonymized.
Job run 1:00 UTC everyday

assignee.information.anonymize.delay

Consolidate tickets purchased in one single email - time-frame

Value: Integer (hour)(count from previous email sending time)
Default value = 0 → OFF feature
The user should only receive one email for the first injected ticket
All other injection during X hours since first email sent will not be sent separately.
After X hours, 1 consolidated injection email will be sent including all ticket-Ids injected.

email.ticket.invitation.nextreceiveperiodtime

Default amount of days after which the unregistered personal information got anonymized

Value: Integer (hour)(count from event end-time)
Default value = 0 → OFF feature
If current time is X hours after event end-time, unregistered account information will be anonymized
Job run 1:00 UTC everyday

personal.information.anonymize.delay

Default amount of time (hour) after which the pending transfers will be cancelled

Value: Integer (hour)(count from transfer initiated)
Default value = 0 → OFF feature
If current time is X hours after ticket is transferred and no accept/reject is done on recipient's side, the transfer will be cancelled.

ticket.approval.cancel.delay

Enable contingent feature

Enable/Disable feature, allowing organizer to filter tickets by contingent

enable.contingent.feature

Hour of the day to send the first reminder, next one will be after the min interval (UTC)

email.reminder.limit.time-first

Interval (in minutes) between split notification campaign schedules

Values: Integer (minutes) (count from the previous notification campaign sent)
If one notification campaign is set with (total impacted spectator) > (Batch size), then after X minutes from the previous sending, the next push notification will be sent.

push.notification.campaign.delay

Values: Integer
In case the organizers use a time-based activation method but do not provide the time, the default value will be applied

Enable Single Email for Bulk Tickets Transfer feature

Values: Integer

Set a specific ticket quantity that triggers consolidated email communication for bulk ticket actions. 

If the action involves tickets equal to or exceeding this number, a single email will be sent. 

For actions involving tickets below the defined quantity, the existing behavior (one email per ticket, including ticket details) will remain

Default value = 2 (set value = 0 to turn OFF feature)

(Minimize the number of emails sent to your spectators for bulk ticket actions)

First name

Mandatory: it is required, spectators need to input on mobile apps

Last name

Mandatory: it is required, spectators need to input on mobile apps

profile.display.lastname

Gender

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

profile.display.gender

Birth date

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

profile.display.birthdate

Nationality

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

profile.display.nationality

Passport number

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

profile.display.passportnumber

Assign reason

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

assign.display.reason

First name

Mandatory: it is required, spectators need to input on mobile apps

assign.display.firstname

Last name

Mandatory: it is required, spectators need to input on mobile apps

assign.display.lastname

Birth date

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

assign.display.birthdate

Email holder

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

assign.display.emailholder

Phone number

Mandatory: it is required, spectators need to input on mobile apps
Optional: it is not required, and visible on mobile apps
Not Visible: it is not visible on mobile apps

assign.display.phonenumber