In Progress
The manual document is in progress. Please expect some features or information missing
ASSIGNMENT FEATURE
Why should organizer use it?
- This feature allows wallet owners to set a holder name for a ticket on their wallet. This is an app-level feature, so when it is enabled, all tickets are available to assign.
How it works?
- To enable/disable feature Assign holder Feature
- If the organizer wants to request for assignment reason, enable the Assign Reason Feature to true.
- If assignment reason is mandatory, set the feature Mandatory Assign Reason to true.
- Text labels for assignment reasons are adjustable on Crowdin.
- Note: for application feature, user needs to kill app and restart to make the feature available after any changes.
- Exception: Main applicant case or when ticket reaches transfer-assign limit (Transfer level >= transfer-assign limit)
How feature is visible on TIXNGO app?
Button available on both ticket screen and floating action buttons
DELETED TICKETS VISIBILITY
Why should organizer use it?
- This feature allows organizer to show deleted tickets screen on app or not.
How it works?
- Once a ticket is deleted with visibility TRUE ("showDeletedTicket":true), user can see this ticket under Deleted tickets screen.
If visibility is FALSE, deleted ticket will not appear on app.
- To enable/disable the feature Deleted Tickets Visibility
How feature is visible on TIXNGO app?
TRANSFER FEATURE
Why should organizer use it?
- To allows user to send ticket to another valid email. Transfer feature is at ticket level, so organizer must define if a ticket can be transfered or not.
How it works?
- A ticket can be transferable or not based on these settings below:
| transferRules.groupId | Transfer rules can technically be different for every ticket. Organizer might want to chose to have different transfer rules for different types of ticket (ex: Adult, child, VIP, etc…). This GroupID is the Transfer rules group ID representing a group of transfer rules applied to certain tickets. If Organizers want to apply the same rules to every tickets, by default this groupID is set to the EventID and every ticket will be in this group. |
|---|---|
| transferRules.maxNumberOfTicketPerPhoneInGroupId | Maximum amount of tickets per phone for this Transfer rules group id. |
| transferRules.maxNumberOfTransferPerPhoneInGroupId | Total amount of transfers per Phone (-1 feature is disabled). |
| transferRules.maxNumberOfTransferPerTicketInGroupId | Total amount of transfers per Ticket (-1 feature is disabled). |
| transferRules.assignTransferLimit | Define upper bound of ticket's transfer level for the "Assign" function |
| transferRules.allowTransfer | Enables or Disables transfer functionality for given match (Send menu item in the ticket view hidden or displayed). |
| transferRules.allowTransferMainApplicant | Enable or Disable transfer functionnality for Main Applicant ticket's. |
| transferRules.allowTransferAfterActivation | Enables or Disables transfer functionality for given match for Activated Tickets (Send menu item in the ticket view hidden or displayed). |
| transferRules.allowTransferAfterActivationByBT | Enables or Disables transfer functionality for given match for Activated Tickets by bluetooth (Send menu item in the ticket view hidden or displayed). |
| transferRules.allowTransferAfterControl | Enables or Disables transfer functionality for given match for Controlled Tickets (Send menu item in the ticket view hidden or displayed). |
| transferRules.keepOneInGroupId | Force ALL ticket wallet holders to keep at least 1 ticket per given Match. |
transferRules.keepOneAtInjectInGroupId | Force ticket wallet holder to whom tickets were originally injected to keep at least 1 ticket per given Match. E.g. all his transfer guests will be able to forward all the tickets they received. |
- Organizer can check if a specific ticket is transferable or not on ticket detail view:
- If organizer wants to request for transfer reason, enable the Transfer Reason Feature to true.
- User can also have option to select language when transfering a ticket (email sending to recipient) in case the recipient has not yet registered an account.
- Language options will be retrieved from app supported languages
- Text labels for transfer reasons are adjustable on Crowdin.
How feature is visible on TIXNGO app?
| string | Indication as screenshot above |
|---|---|
| transfer_functionality_description | description on ticket screen |
| transfer_functionality_title | |
| recipient_confirmation_page_description | description on confirmation screen |
| transfer_multiple_ticket_option | select more tickets to send |
| transfer_recipient_empty_value |
TRANSFER ALERT IF DIFFERENT LOCATIONS
Why should organizer use it?
- This feature allows organizer to set up a pop-up alert to remind user transfering tickets in case user has multiple tickets (same event) with different locations (Gate/Block..)
How it works?
- Enable the feature on app level: Transfer alert for ticket owner has multiple tickets in different locations to TRUE
- Define which kind of location: Select which seat details to alert the different location at Ticket Owner Transfer Alert Keys
- Define the 1st time to show pop-up: configuring Number of hours before event start time sending different-gates/blocks first message in the app.
Meaning (x)hours before event starts, pop-up will appear. - Set up interval: define at Number of minutes before sending different-gates/blocks reminder in the app.
How feature is visible on TIXNGO app?
Example:
- user A has 3 tickets for event 1 and 2 tickets with Gate A, 1 ticket with Gate B.
- 3 hours before start time, pop-up appears asking user to send tickets to make sure user go to correct gate
- At scheduled time, a pop-up is showed as below
| string | Indication as screenshot above |
|---|---|
| diff_location_reminder_title | title of the pop-up |
| diff_location_reminder_body | content of te pop-up |
| diff_location_reminder_1st_btn | Transfer tickets now button |
| diff_location_reminder_2st_btn | Maybe later button |
NON-TRANSFERRED TICKETS REMINDER
Why should organizer use it?
- To encourage users to send tickets to other spectators in case they hold 2 or more tickets for one event by showing an in-app pop-up reminder.
How it works?
- Enable the feature: upon request and need the implementation on mobile side (require new build)
- Interval time: define at Number of minutes before sending a non-transferred reminder in the app
- If interval = 0, pop-up will be disabled and only yellow ribbon will appear on event level
How feature is visible on TIXNGO app?
Example:
- user A has 3 tickets for event 1
- Once user opens app the 1st time, pop-up appears reminding user to send tickets to guests
- The pop-up goes along with yellow ribbon stayed on event level
- Pop-up will periodly appear after an interval
| string | Indication as screenshot above |
|---|---|
| transfer_warning | content of ribbon for non-transferred tickets pop-up |
| transfer_dialog_warning | content of pop-up for non-transferred tickets |
| assign_or_transfer | |
| close |
NON-ASSIGNED TICKETS REMINDER
Why should organizer use it?
- To make sure organizer can collect all necessary ticket holder information that associated to each ticket.
- The feature include:
- A pop-up asking for assigning tickets in case user has any non-assigned ticket for an event
- A red banner covering QRcode section to alert users when a ticket has not yet assigned.
The red banner will remain until the ticket is assigned and change to neutral grey color if assignment is made.
How it works?
- Enable the feature: upon request and need the implementation on mobile side (require new build)
- Interval time: define at Number of minutes before sending a non-assigned reminder in the app
- If interval = 0, pop-up will be disabled and only red banner will appear on ticket level
How feature is visible on TIXNGO app?
| string | Indication as screenshot above |
|---|---|
| non_assign_title | title of the red ribbon & pop-up |
| non_assign_subtitle | subtitle of red ribbon & pop-up |
| assign_reminder_1st_btn | Assign ticket now button |
| assign_reminder_2st_btn | Do it later button |
FORCE UPGRADE APP VERSION
Why should organizer use it?
- It is important to keep all the fans up-to-date on the latest version of your apps to ensure all new features, bug fixings and performance improvements for them
How it works?
- Make sure organizers have the latest usable version released and the minimal version they want to support (format: x.y.z , ex: 1.0.1)
- Define the latest version at Latest version of mobile application
- Define the minimal version at Minimal supported version of mobile application
- To disable the feature, set both value to 0.0.0
How feature is visible on TIXNGO app?
If user's app matches minimal version but not latest version:
If user's app is lower than minimal version:
| string | Indication as screenshot above |
|---|---|
| upgrade_title_available | title of the pop-up (not required) |
upgrade_text_available | content of the pop-up (not required) |
| upgrade_title_required | title of the pop-up (required) |
| upgrade_text_required | Content of pop-up (required) |
| upgrade_button | Upgrade button |
| not_now | Not now button |
UPDATED LEGAL DOCUMENT CONSENT
Why should organizer use it?
- To make sure your fans are aware of the new version of your app's legal document
- Request end-users consent can help you ensure that all fans have read and accepted the new document
How it works?
- Go to Application Settings, set up latest version at Request all users to consent to updated legal documents (version)
- If organizers want to disable the request by any reason, redefine the value as -1
How feature is visible on TIXNGO app?
| string | Indication as screenshot above |
|---|---|
| legal_docs_reminder_title | title of the pop-up for requiring consent updated legal docs |
| legal_docs_reminder_body | content of pop-up for requiring consent updated legal docs |
| legal_docs_reminder_1st_btn | Confirm button on pop-up |
LIMIT MAX ACTIVE DEVICES
Why should organizer use it?
- To help avoiding multiple users logging into one account at the same time (from different devices)
- It provides an extra layer of security that can reduce the risk of fraudulent activity
How it works?
- Enable the max active devices feature at Enable max amount of active devices security under Application Settings
- Define the max active devices that you allow user to login at the same time per account
- If Enable online/offline check if device reached max active sessions below is false and account reaches max active number:
- User can't log in on other devices
- If Enable online/offline check if device reached max active sessions below is true and account reaches max active number:
- User can log in on other devices if previous devices are online or offline within 122 seconds
- Account will be logged out from previous device.
How feature is visible on TIXNGO app?
For example: feature is enabled and set to 1 max active device.
User A is on device 1 successfully.
User A or B, then try to log in again with same account on device 2.
After loading for a few seconds, pop-up showed to inform user can't login on device 2.
As soon as account is logged out from device 1, it's possible to re-join with device 2.
| string | Indication as screenshot above |
|---|---|
| max_login_title | title of the pop-up for limit max active session - Failed to login |
| max_login_msg | content of the pop-up for limit max active session -Failed to login |
| log_out_other_phone_msg | when user tries to login on a device and system tries to logthem out from another device |
TRANSFER MESSAGE
Why should organizer use it?
- To enrich fan's experience, now users can include a message when transferring their tickets to another user.
- Once the transfer is complete, the recipient could receive a message from the sender as a part of the email
How it works?
- Enable the feature at app level under Enable message box when transfer ticket
- Include the parameter $$message$$ in your transfer templates to make sure recipient can see the content of it
How feature is visible on TIXNGO app?
.png?version=1&modificationDate=1676540392191&cacheVersion=1&api=v2&width=184&height=400)
The email of transfer:
Crowdin?
| string | Indication as screenshot above |
|---|---|
| only_one_transfer_ticket | 1 Ticket (Send your ticket screen) |
| transfer_message_input_title | Message (Send your ticket screen) |
| transfer_functionality_description | the description explains transfer function (Ticket screen) |
| transfer_functionality_title | Send your ticket (button) |
| add_recipient_email | Add recipient email (button) |
| recipient_confirmation_page_description | You can send tickets to someone else directly within the app. Simply follow the steps below. |
| transfer_recipient_empty_value | Add email address of ticket recipient |
DYNAMIC LOAD FROM CROWDIN
Why should organizer use it?
- Message and content showing on app might constantly change based on organizer's need and it used to require a new build for any change
- User must update new app version in order to see any changes, so it takes time and we're unsure that all users are up to date
How it works?
- Make sure the current application build include dynamic load feature
- Enable the feature at application feature: Dynamic load from Crowdin
- Step involves to integrate the latest Crowdin version on app:
- Update the translations and make sure to save and approve them
- Go to Project\Translations
- Click on Build & wait for the progress to be done
- Refresh the app and see new translations
