Understand the Settings page

For the details of each key, make sure you check the section here.

Application settings

Go to Settings page > Click Application settings tab

Those settings are related to some specific features that will display or work on the app. Below are all related features that you can configure:

Force Upgrade & Update:

In case your application has a new build (version) and you would like to force every user to be up to date.

• Under Settings > Application settings, looking for these 2 keys to define your latest or minimum supported version.
  • version.latest (Latest version of mobile application)
  • version.minimal (Minimal supported version of mobile application)

• To force users to upgrade to the latest version (if not upgrade, user won’t be able to use the app), fill the latest mobile app version at key mobile.version.minimal
• To give users the option to upgrade or not (if not upgrade, user can still use the app), fill the latest mobile app version at key mobile.version.latest

Limit max active devices at once:

This feature allows organizer to limit the number of active sesstion for 1 account at once per app.

In order to enable this feature, under Settings > Application Settings, organizers need to:

• Set the key security.session.use-max-active-phone to true (Enable max amount of active devices security)
• Define the max value that you want to limit user at key security.session.max-active-phone (Max number of active devices at once)

For more advanced restriction: to disable/enable the possibility of checking online/offline check if device reached max active sessions (Disable online/offline check if device reached max active sessions):

• Set key security.session.disable-online-check to true: show dialog error immediately so user can't login on new device
• Set key security.session.disable-online-check to false: Check online/offline (less than 2mins 2secs) => if offline show dialog error, if online kickout the user

Limit Only one active wallet session:

This feature can quickly help organizer to set up the limitation for only 1 device instead of setting multiple keys for max active devices:

• Set key security.session.only-allow-one (Only one active wallet session is allowed) to true

Note: these 2 limit active session feature should not be enabled at the same time.  

Assign reminder for non-assigned tickets:

• Use case: you want to remind user to always assign a name as ticket holder for every ticket they have. This feature is useful to allow organizer to do it.
• Non-assigned reminder allows organizer to set pop-up reminder in case user has at least 1 non-assigned ticket for an event in their wallet.
  
• This feature is only block QR to be showed until ticket is assigned/kept for myself
  
• How to enable the feature: feature must be switched on from mobile side (new build required)
  
• Once feature is enabled, non-assigned reminder will always display until user has no non-assigned ticket left on their app. Based on the interval time set by organizer, reminder will appear after an amount of time. 
• Organizer can set up the interval time between 2 pop-ups time on Back-Office at Number of minutes before sending a non-assigned reminder in the app. If value = 0, pop-up will be disable. 
  
  
• There’s also a ribbon covering QR-code part and displayed on non-assigned ticket indicates the message to ask user assign ticket. This ribbon is always showed regardless of interval value and text is editable on Crowdin. 

Transfer reminder for non-transfered tickets

• Use case: you want to remind user to transfer their tickets (only allow to keep 1 ticket per event). This feature is useful to allow organizer to do it.
• What will be displayed on user’s app:
  • When user opens app for the first time, a pop-up message in app for transfering ticket reminder shown. The content of pop-up is editable and translatable on Crowdin for each app.
  • If the transfering is not made by user, pop-up will be shown again after interval time that being set on Backoffice.
    
    
• Interval time in minutes (between 2 pop-ups) is defined at key ticket.non-transferred.reminder (Number of minutes before sending a non-transfered reminder in the app) and must be greater than 0

Different seat details reminder:

• User case: user has multiple tickets for 1 event, but different seat details (Block/Gate/Row..), and organizers want to remind users to transfer those tickets with specific seat details.
• The organizer needs to enable the feature need to:
  • Set key to true: owner.transfer.alerts (Transfer alert for ticket owner has multiple tickets in different locations) – Settings > Application Features

• Define the time for the first reminder pop-up via key owner.transfer.alert.hour (Number of hours before event start time sending different-gates/blocks first message in the app)
• Define the interval time between 2 pop-ups via key ticket.owner.transfer.alert.interval (Number of minutes before sending different-gates/blocks reminder in the app)
• Define the key to compare tickets with different seat details via key ticket.owner.transfer.alerts-keys (Ticket Owner Transfer Alert Keys)
• What will be displayed:
  • X hours before the event start time (setting above), a pop-up message in app for transferring tickets shown. The content of pop-up is editable and translatable on Crowdin for each app.
  • If there’s no action from the user, pop-up will be shown again after interval time.

Protect screenshot and screen recording:

This is an on-demand feature and is only available for a paid package.

• Use case: organizer want to prevent users from having QR code in their screenshot and screen recording on their app, but still want to have the option to enable that in some cases.
• Enable the feature on mobile: set key screen.protect.shot.record to true (Protect screenshot and screen recording) 
• Configure the special code for disable/enable the feature via key screen.protect.shot.record.secret-code

Customize Ticket Details displayed on Activation Screen

• Under Application Settings, find the key design.activation.ticket-details-key (Ticket detail key that displayed on activation screen)
• Select from the dropdown list which value you want to show on the screen

What will be shown on mobile:

Application features

Under application feature tabs, an organizer can enable/disable a feature on the app by setting the key to a true/false value.

For a full list of those features available, please make sure you check this section

Key features:

Assignment functionality

Key:  assign-holder

Purpose: this feature will enable the assignment feature on the whole app

Deleted Tickets Visibility

Key: deleted-tickets-visibility

Purpose: to display the deleted tickets tab on app

Mandatory Assign Reason

key:  mandatory-assign-reason

Purpose: Request mandatory reason for assignment

Protect screenshot and screen recording

Key: screen.protect.shot.record

Purpose: Prevent screenshot and video recording 

Transfer alert for ticket owner has multiple tickets in different locations

Key:  ticket.owner.transfer.alerts

Purpose: Reminder in case user has tickets in different locations 

Select language when transferring ticket

Key: transfer-language

Option to select language when transfering 

Transfer Reason Feature

Key: transfer-reason

Purpose: Request reason for transfering ticket 

Bluetooth Feature

Key: use-bluetooth

Purpose: to enable the Bluetooth activation feature on app as well as ribbon guideline to user. 

Note: for ribbon guideline to be displayed, organizer must enable bluetooth feature and input the  bluetoothPreparationRibbonDisplayTime value. 

Wristband Activation Feature

Key: wristband-activation 

Purpose: to enable the Wristband activation feature on app

How to use: during ticket injection, ticket hidden field (ticketDetails.hidden) must be defined with key-value of key = hosp_room and value

Organizer settings:

Consolidate tickets purchased in one single 

• Sometimes, receiving multiple emails for a batch of purchased tickets can be really confusing to users. So this feature helps to consolidate multiple newly injected tickets to only one single email in a period of time. 
• The default value should be 0, which means this feature is not Active
• With that feature enabled, 1st emailing is generated right after the very first injection. Then after the interval time (value to be set), another email will be sent including the rest tickets injected during the internal time.
• Unit timeframe: hour

Setting delay time for transferred ticket auto-cancellation

• This feature dedicates the delay time auto-cancellation when a transfer transaction passes a delay time that is set by the organizer, but the recipient still does not accept/reject the ticket.
• Delay unit: hour

Setting reminder emails for non-register users

• This feature is useful to remind those non-register users who have tickets on TIXNGO but have not yet downloaded and created an account on the app. 
  
  
• In order to send a reminder email, the organizer needs to set these 4 keys below:
  • email.reminder.limit.days-first : Number of days before the Event to start sending reminders
  • email.reminder.limit.time-first : Hour of the day to send the first reminder, the next one will be after the min interval (UTC)
  • email.reminder.limit.min-interval: Minimum interval between two reminders in hours
  • email.reminder.limit.max-number: Max number of reminder emails that can be sent per ticket

Setting limited batch for push notification campaign

• As a solution to avoid performance issues during the creation and sending notification campaigns, we recommend organizers define the batch size and interval time between 2 splited schedules. 
• There are 2 keys on Back-Office to help you define that:
  • push.notification.campaign.batch_size: Push notification campaign batch size
  • push.notification.campaign.delay: Interval (in minutes) between split notification campaign schedules

For more information on the Push Notification Campaign, please check this page. 

Setting default time for anonymizing unregistered user's personal information

• Based on the GDPR compliance,  in some cases, organizers might need to anonymize unregistered users' personal information after a period of time.
• On Back-Office (Organizer settings), organizers can set up an automatical job to do it by configuring the key below:
  
  • personal.information.anonymize.delay: Default amount of days after the event expired date which the unregistered personal information got anonymized

.