From the LS Activity Role Center you can access different setups by using the Administration menu in the Role Explorer navigation menu.
From the Activity Manager Role center menu you also have access to different setups.
The table below lists some of the setups that are mostly available in the Setup menu (under Administration).
| Setup | Description |
|---|---|
| No. Series | Set up the number series to use for issuing a Ticket Barcode as reference in the admission entry. |
| Status Setup | On the relevant status settings, the Admission Handling must be set up to either Issue Admission or Cancel Admission. Normally at the Confirmation Status and the Cancel Status. |
| Label Types | If you need to print paper tickets using script-based printers, you must create a Label template which dictates the layout (script). Normally, the script will use field value inserts from the Activity Admission table (each ticket will be an entry in this table). See the script setup on the related label type. The syntax of the script is determined by the printer or printer driver being used to produce the output (ticket). |
| Label Printing | This setup determines what printer will be used to print the ticket or label based on the Business Central user login. Here it is possible to specify Default for using normal Business Central printing and the printer is selected by the standard Business Central printer selection mechanism. Preview shows the output on the screen. The third option is LS Hardware Station and you can select the printer name from available Hardware Station settings. Note: Label printing is only used if the Activity product is using labels to provide the output. |
| Business Central Report | If you need to use a standard Business Central report to provide the actual ticket, you can create a report based on the Activity Admission table and assign it on the activity product as the admission output. Consult with your partner or LS Consulting for more information about creating such a report. |
| Product | You must create an Activity Product as the basis of the ticketing. This product can either be depending on availability (having resources defining availability) or it can be issued and tickets printed without having availability requirements. To be issued as an admission, the product must have the following settings assigned:
|
| POS and POS commands | To sell a ticket on the POS, you use the SELLPRODUCT POS command as any other activity product. You can also use the CHANGETICKET POS command to change Quantity and Dates and Times on an existing journal line. The POS action TICKETPRINT must be in place to automatically print tickets which are being posted at the POS. Note: Do not have this POS action activated, if there is no ticket printing required in the implementation. Otherwise, the action might slow down the finalizing of the sale and it is not necessary unless printing is needed. Tip: You can use the CHECKACCESS POS command to enter the barcode reference and check if the ticket is valid. |
There are two ways to sell tickets:
- By booking the activity product presenting the ticket as you would book any other activity product. If you need to send the tickets or barcodes to the client, you should use the confirmation emailing mechanism to "print" the tickets as attachment to the confirmation email. The report must be based on the Activity Reservation table and list all related Activity Admission entries that are linked to the reservation.
- Sell the related ticket (activity product) on the POS like any other activity product and issue the paper tickets via the label mechanism or Business Central report. Tickets can also be issued via method 1 using the email confirmation process.
Both methods will issue an Admission entry record for each ticket sold and booked. Later, you can check and confirm the access using either the POS (with the CHECKACCESS command) or the web APIs. In the LS Activity Manager role center use the Issued Admission cue to see when ticket products are confirmed in BackOffice or via API or sold at the POS.