...
Variable Name | Variable Description | Backend Key |
Assign Holder Feature | Enable / Disable assign-holder feature, allowing spectator to assign a ticket to a Holder | assign-holder |
Bluetooth Feature | Enable / Disable Bluetooth feature, allowing preparation beacon behavior (Only allow ribbon (what is ribbon? How to see colored information ribbons) and reminder "activate Bluetooth" to be showed, Bluetooth Scanner always enable to scan tickets even this feature is enable or not, even on match day or not) | use-bluetooth |
Display Ticket Owner Feature | Enable / Disable display-owner feature, allowing Owner name to be displayed on the ticket | design.display-owner |
Assign Reason Feature | Enable / Disable assign-reason feature, allowing spectator to give a reason when assigning a ticket to a Holder | use-assign-reason |
Transfer Reason Feature | Enable / Disable trasnfer-reason feature, forcing spectator to give a reason when transferring a ticket | transfer-reason |
Mandatory Assign Reason | Enable / Disable assign-reason feature, forcing spectator to give a reason when assigning a ticket to a Holder | mandatory-assign-reason |
Select language when transferring ticket | Enable / Disable transfer-language feature, allowing spectator to select language of email template when transferring ticket | transfer-language |
Deleted Tickets Visibility | Enable / Disable deleted-tickets-visibility feature, displaying deleted tickets on mobile application | deleted-tickets-visibility |
Wristband Activation Feature | Enable / Disable wristband-activation feature, allowing organizer to activate tickets have wristband option (e.g. hospitability room) | wristband-activation |
Transfer alert for ticket owner has multiple tickets in different locations | Enable / Disable ticket.owner.transfer.alerts feature, allowing organizer to notify for ticket owner has multiple tickets in different locations to transfer tickets. (Dependent with ticket.owner.transfer.alerts-keys and ticket.owner.transfer.alert.hour) | ticket.owner.transfer.alerts |
Organizer Settings
Variable Name | Variable Description | Backend Key |
Max number of reminder emails that can be sent | Values: Integer [0, 5] (maximum of 5 reminders per person Type: email | email.reminder.limit.max-number |
Minimum interval between two reminder in hours | Values: Integer >= 12 (limits to a maximum of 1 email every 12h, hence 2 per day max) Type: email | email.remidner.limit.min-interval |
Time of the day to send the first reminder | Values: Integer [0, 23] representing hours of the day Type: email | email.reminder.limit.time-first |
Number of days before the Event, to start sending reminders | Values: Integer >= 0 Type: email | email.reminder.limit.days-first |
Amount of time (hour) after which the pending transfers will be canceled (Set 0 to not auto-cancel pending transfers) | Values: Integer >= 0 Value indicates the number of hours before auto-cancel is triggered (Value = 0 : no auto-cancel) | ticket.approval.cancel.delay |
Consolidate tickets purchased in one single email - timeframe (X hour) | · Value: Integer (hour) Default value = 0, which mean this feature is not Enable. · The user should only receive one email for his first injected purchased ticket. · The system shall block any purchase emails for X hours after the first sending of email for each ticket holder (counting separately for each ticket holder). · If the X (hours) time is past, those emails that are generated in X time will never be sent. | email.ticket.invitation.nextreceiveperiodtime |
Amount of days after which the unregistered personal information got anonymized (Set 0 to disable) | · Automatic anonymization processing X days after the event ended · Set 0 to not auto anonymize unregistered users · Automatic anonymization processing X days after the event ended, X get from the configuration · run every night (ex: 1:00 am server time) · Value: interger >= 0 | personal.information.anonymize.delay |
...