Index
Club requirements
The club requests integration with the GetSelect APIs of the following functionalities:
- With each reservation made, the getSelect server must be requested to create a single-use code to extract the balls.
- The validity/usability of said code will expire after 15 minutes from the date/time stated in the reservation.
- This code must be sent in QR form along with the reservation confirmation email.
- The reservation panel must reflect whether the client has used the code or not. has used it. In the event that you use it, the reservation must be marked as "check in". In the event that 15 minutes elapse and the code is not used, the reservation must be marked as "not presented".
- Be able to add the QR code(s) to the sales ticket when selling ball tickets from the POS. This involves a unique code request to the servers, identical to that for reservations.
Module configuration/installation
The first thing we must do is install the module from the appMarket as usual. The module is called "getSelect". Once installed, a submenu called "getSelect" will be added within the GM configuration menu with the following options:
- User name (userName)*
- Access key (passKey)*
- Tenant identifier: (tenantId )*
- Application identifier: (appId)*
- Member email (email)**
- Balls product (ballsProduct)
- Quantity of balls (ballsQuantity)
- Enable synchronization with the server (getSelectCronJobEnabled)* Must be provided by getSelect* * This email must be registered by the client/club according to the getSelect instructions. The rest of the options are self-describing; The ball product option is used to
choose the product that is associated with the sale of balls so that the corresponding ball QR can be printed on the ticket from the POS. By default, when the module is installed, the option to "enable the "server synchronization is disabled" to prevent it from running before it has been configured
Ball machine
correctly getSelect the module.
Functioning
This module does not include UI itself; when we generate a reservation, gm
will attempt a request to the server (configured above) to obtain a unique balls code for that reservation. This code will be sent as a QR attached to the reservation confirmation email that the club has configured. The latter is independent of the email template used, since the code goes in the attachments. This code is the one that the end customer must pass through the scanner of the ball machine. From the POS, when we finalize a sale that contains a line with the product chosen in the configuration, the system will try to request the corresponding codes, but this time, instead of by email, it will print them on the sales receipt so that they can be passed in front of the machine.
Considerations
The club has decided that the code must expire after 15 minutes from the
date/time indicated in the "start" field of the reservation.