The Settings page allows the organizers to list and customize the TIXNGO user experience by enabling features on BackOffice and on Mobile.
From this page, you can change the current setting by clicking the Edit icon. If the Edit icon is not visible, please reach out to your PS team.
The full list of Settings & Keys are now available in this page : https://confluence.secutix.com/x/FpUvCg
This page includes all setting keys available on TIXNGO Backoffice which allow organizers to configure on their own.| Table of Contents |
|---|
Where will you see it?
- Go to Settings Page > Select the correct Mobile App ID
Detailed setting keys
Application Settings
...
Variable Name
...
Variable Description
...
Backend Key
...
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
...
Disable online/offline check if device reached max active sessions
...
Values: FALSE, TRUE; disable or enable the online check if device readed max active sesssions.
(For login restriction security purpose)
...
security.session.disable-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
...
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
Application Features
...
Variable Name
...
Variable Description
...
Backend Key
...
Assign Holder Feature
...
Option to add a name on a ticket with other required information that can be set up under Assignment Configuration.
...
assign-holder
...
Deleted Tickets Visibility
...
Option to display deleted tickets under the section "Deleted Tickets" in the menu.
...
deleted-tickets-visibility
...
Enable quick manual activation feature
...
Manually activate a ticket by tapping on the Event Number area (on the right side of the ticket image) to go to the next screen and by tapping the yellow icon. This functionality only works the day before the event and during the day of the event.
...
quick-manual-activation
...
Protect screenshot and screen recording
...
Protect active QR codes from screenshots and screen recordings. Whenever these actions will be taken, the active QR code is covered with red text “This is a screenshot, not a valid ticket”.
...
screen.protect.shot.record
...
Transfer alert for ticket owner who has multiple tickets in different locations
...
Turn on the functionality to send an alert about conflict within tickets with different seating details in one wallet
(Dependent with ticket.owner.transfer.alerts-keys and ticket.owner.transfer.alert.hour)
...
ticket.owner.transfer.alerts
...
Enable built-in encryption for activation/deactivation pin
...
For secure purposes, if this key is set to true, the Manual Activation ID will be encrypted on mobile local storage
...
ticket.pin.allow-encrypted
...
Select language when transferring ticket
...
Add an additional step on the transfer screen and allow a spectator to choose the language of emails that will be sent to the ticket recipient.
...
transfer-language
...
Transfer Reason Feature
...
Spectators will be asked to choose a predefined reason while transferring tickets (sending tickets via mail).
...
transfer-reason
...
Bluetooth Feature
...
Enable/Disable feature, allowing preparation beacon behavior and its related reminder.
...
use-bluetooth
...
Wristband Activation Feature
...
Enable/Disable feature, allowing organizer to activate tickets have wristband option (e.g. hospitability room)
...
wristband-activation
Organizer Settings
...
Variable Name
...
Variable Description
...
Backend Key
...
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
...
Multilingual Settings
...
Variable Name
...
Variable Description
...
Backend Key
...
Burger Menu: Item 1 Title
...
Title of the menu item for the external website
...
promo.external.menu.title
...
Burger Menu: Item 1 Description
...
Sub-text of the menu item for the external website
...
promo.external.menu.description
...
Event List: Promo 1 Title
...
Title of the box in the event list for the external website
...
promo.external.event.title
...
Event List: Promo 1 Description
...
Sub-text of the event list for the external website
...
promo.external.event.description
...
Event List: Promo 1 URL
...
Multilingual link to an external website
...
promo.external.link
...
Burger Menu: Item 2 Title
...
Title of the menu item for the other app
...
promo.otherapp.menu.title
...
Burger Menu: Item 2 Description
...
Sub-text of the menu item for the other app
...
promo.otherapp.menu.description
...
Event List: Promo 2 Title
...
Title of the box in the event list for the other app
...
promo.otherapp.event.title
...
Event List: Promo 2 Description
...
Sub-text of the event list for the other app
...
promo.otherapp.event.description
...
Event List: Promo 2 URL
...
Multilingual link to an other app
...
promo.otherapp.link
...
App download link in Emails
...
Multilingual link to branded app
...
app.dl.link
...
App name in Emails
...
Multilingual app name
...
...
Push Notifications at ticket injection content
...
Content of the push notification recieved at injection
...
notification.inject.content
...
Push Notifications at ticket injection title
...
Title of the push notification recieved at injection
...
notification.inject.title
...
Push Notifications transfer recipient content
...
Content of the push notification recieved by recipient of transfer
...
notification.received.content
...
Push Notifications transfer recipient title
...
Title of the push notification recieved by recipient of transfer
...
notification.received.title
...
Push Notifications transfer sender content
...
Content of the push notification recieved by sender of transfer
...
notification.sent.content
...
Push Notifications transfer sender title
...
Title of the push notification recieved by sender of transfer
...
notification.sent.title
...
Push Notifications at ticket deletion content
...
Content of the push notification recieved when a ticket is deleted
...
notification.deleted.content
...
Push Notifications at ticket deletion title
...
Title of the push notification recieved when a ticket is deleted
...
notification.deleted.title
...
Push Notifications at ticket activation content
...
Content of the push notification recieved when a ticket is activated
...
notification.activated.content
...
Push Notifications at ticket activation title
...
Title of the push notification recieved when a ticket is activated
...
notification.activated.title
...
Push Notifications at transfer cancelation content
...
Content of the push notification recieved when a transfer is canceled by sender
...
notification.cancel.content
...
Push Notifications at transfer cancelation title
...
Title of the push notification recieved when a transfer is canceled by sender
...
notification.cancel.title
...
Push Notifications at transfer accept title
...
Title of the push notification received by sender when transfer is accepted by the receiver
...
notification.acknowledge.accepted.title
...
Push Notifications at transfer accept content
...
Content of the push notification received by sender when transfer is accepted by the receiver
...
notification.acknowledge.accepted.content
...
Push Notifications at transfer reject title
...
Title of the push notification received by sender when transfer is rejected by the receiver
...
notification.acknowledge.rejected.title
...
Push Notifications at transfer reject content
...
Content of the push notification received by sender when transfer is rejected by the receiver
...
notification.acknowledge.rejected.content
...
Push Notification at session logout title
...
Title of the push notification received by a user at session logout
...
notification.logout.title
...
Push Notification at session logout content
...
Content of the push notification received by a user at session logout
...
notification.logout.content
...
Email subject at ticket injection
...
Email subject received by initial spectator when a ticket is injected
...
email.invitation.inject.subject
...
Email body at ticket injection
...
Email body received by initial spectator when a ticket is injected
...
email.invitation.inject.body
...
Email subject at ticket transfer to unknown account
...
Email subject received by recipient of transfer when account is not in TIXNGO system
...
email.invitation.approval.subject
...
Email body at ticket transfer to unknown account
...
Email body received by recipient of transfer when account is not in TIXNGO system
...
email.invitation.approval.body
...
Email subject at ticket transfer to known account
...
Email subject received by recipient of transfer when account is already in TIXNGO system
...
email.information.approval.subject
...
Email body at ticket transfer to known account
...
Email body received by recipient of transfer when account is already in TIXNGO system
...
email.information.approval.body
...
Email subject at ticket transfer cancellation
...
Email subject received by recipient of transfer when transfer is cancelled
...
email.information.cancel.subject
...
Email body at ticket transfer cancellation
...
Email body received by recipient of transfer when transfer is cancelled
...
email.information.cancel.body
...
Email subject for reminders
...
Email subject received when spectator gets a reminder (has not downloaded his ticket yet)
...
email.reminder.subject
...
Email body for reminders
...
Email body received when spectator gets a reminder (has not downloaded his ticket yet)
...
email.reminder.body
...
Email subject at ticket deletion
...
Email subject received by spectator when a ticket is deleted
...
email.delete.subject
...
Email body at ticket deletion
...
Email body received by spectator when a ticket is deleted
...
email.delete.body
...
Email subject at transfer has been auto_canceled successfully (to recipients)
...
Email subject received by spectator(transfer receiver) when a ticket is auto_canceled
...
email.information.automaticallycancel.recipient.subject
...
Email body at transfer has been auto_canceled successfully (to senders)
...
Email body received by spectator(transfer sender) when a ticket is auto_canceled
...
email.information.automaticallycancel.sender.body
...
Registration Configuration
...
Variable Name
...
Variable Description
...
Backend Key
...
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
...
Assignment Configuration
...
Variable Name
...
Variable Description
...
Backend Key
...
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
...