The bikubo app can be installed on iOS and Android devices. The download links of one and another repository are:
The online validation makes the checks to be made regarding the readings of the QRs/barcodes and/or the pagers, look at the bikubo server databases, so that the Data is unique for all validators. Thus, if the 'validator A' validates a ticket, it is put as VALIDATED, so if you try to access with that ticket again by the same validator or by 'validator B' (if you are also validating online), it will appear as validated and the app will show you the error. It is important that the validator selects the Validation menu option (Event - ticket category) that interests him, since when validating a ticket, if the app considers it valid, directly the delivery and the next time the app is validated, will show as VALIDATED previously.
In the menu of the app you have the button 'Update Menu', with the functionality of refresh the options of Events and categories of tickets possible to validate, in case the administrator has added new events or tickets categories. In this way it is not necessary for the validator to close the session and start a new one to take the changes.
In addition, the online validation allows the data to be the same for all the validators, that is, they will see the same validated tickets, with the same order of delivery.
When having to access the bikubo server, it is necessary to have a good internet connection so that the process is carried out correctly.
The steps to be carried out to validate online at the door are as follows:
-
Open the app on the device.
-
Log in with the user and password. This data is displayed on the bikubo intranet, on the 'My details' screen.
-
Select in the main screen 'Validate against Server'. It is the option that is selected by default after login.
-
As an administrator can have different events active, each with different categories of tickets, the app allows the validator to select from the menu - validations, the event and ticket category that can be validated, or for an event, validate all the tickets. The option that is selected by default, is to validate for all events, all tickets. So, according to this, what option does bikubo advise to select?
If the title event 'My event' is organized in such a way that an attendee with a ticket associated with a certain access (for example Door A), then the validator that is put on that door, must select from the menu - Validations , the option 'MY EVENT - Door A'. The app will only show the valid tickets of type Gate A of the event 'My event'.
If the title event 'My event' is organized in such a way that all the attendees can enter through the same access door, despite having different categories of tickets (General, VIP), then the validator that is put in that door, you must select from the menu - Validations, the option 'MY EVENT - All tickets'. The app will show all the tickets of the 'My event' event as valid, not other events.
The option 'ALL EVENTS - All tickets' is the one selected by default. The app will show as valid all the tickets of any active event that the administrator has.
-
To scan a QR/barcode, click on 'Open scanner', and activate the camera to proceed to the focus of the same towards the QR/barcode.
-
After scanning, if the ticket is valid, the ticket information associated with it is displayed (Event name, ticket category, ID and/or attendant name if applicable). There is also an identifying OK sound. At the moment that information is displayed, the ticket is already VALIDATED, so the next time it is scanned, it will be indicated that it has been previously VALIDATED. If the ticket contains an identification data of the attendee (name and/or ID), the validator action is required, press the button to exit the information screen of the ticket. If attendee information is not displayed, the ticket information remains displayed for less than three seconds and returns to the scanning position for the validation process to be agile.
-
You can also validate a ticket by manually entering the locator, after clicking on 'Write reference' and then 'Check reference code'.
-
If the ticket has been canceled, or is not valid for the user, or has been previously VALIDATED, a red box indicating the information is displayed. There is also an identifying error sound.
-
The app shows on the screen a history of errors, which we consider useful for the validator, to inform you of whether that attendee or that ticket has been erroneously validated previously, the type of error, and the dates of previous validations. It also shows information associated with the ticket, so that the validator can make pertinent checks (the distributor that assigned it, name and/or ID of the attendee, email, date of sale, ...).
-
You can see the list of validated tickets by clicking the 'data' tab. It lists the events with their ticket categories, and validated tickets with reference to the printed and electronic tickets generated. The format shown is of the following type:
Event name; Ticket Name; Valid Tickets/Generated Tickets
If you click on a ticket category, the list of generated tickets is displayed, sorted by the most recent validation date to the oldest one, and after the validated ones, the unvalidated ones are shown.
The data for each ticket shown is:
-
The locator. It is not shown complete for the attendee's security.
-
Validation status: VALIDATED, ACTIVE.
-
Validation date: the date and time of ticket validation.