Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Other Improvements
- Operators can now use Thermal Ticket Printing with RFID capabilities on the supported Stimare Printer. The RFID tag embedded on the Thermal Ticket will then be linked to the printed ticket, transferred to the access control system (through our API), and can be used as access control identification.
- Date format of your reports can now be tweaked to match your local format. To change the date-time format of your reports, please reach out to our customer service. The team will be able to adjust the institution parameters where the definition of the date format is set for reports. So all your reports can now display dates in format such as "mm.dd.yyyy hh:mm:ss" or "dd.mm.yyyy hh:mm:ss".
- External Reference for Movements is now available on the ticket template editor, which can then be displayed on the thermal ticket or to be sent to TIXnGO as extra ticket fields.
- The automatic refund batch was refunding installments having failed to be paid. From this release, operations having a due date agreement linked that has not been paid or where the payment has failed will be excluded from the automatic refund process.
- Search for tickets by card number by scanning an RFID tag, from the on-site support screen.
- Take history into account when limiting the quantity per order or performance in advantages
- Automatically push the access control checks to TIXnGO.
- Prevent injection of tickets to TIXnGO for which ticket holder data is missing.
- (Tournament platform) It is now possible to use the sub-target group's code and name (linked to a B2B relay contact) as a dynamic field/macro so that you can further customize the Invoice and File Summary documents and provide personalized content based on the File Contact's sub-target group.
- Reprinted TIXnGO tickets will be injected to the latest owner by default but can be sent to the original owner based on the invalidation cause.
- Operators can revalidate a contact that was inactivated, e.g. due to contact merging. Note that this does not fully revert the invalidation/merging process: merged transactions or deleted names will not be restored.
- NEW V3.15 In the touch cart, your operator selling merchandising can see at a glance the current stock level of items (either for the stock locations of the PoS if defined or the overall stock). An out-of-stock icon
is shown when the stock is lower than the quota alert threshold. - NEW V3.15 More contact titles are now available for customers in DACH and UK: you can activate the new values for the title from Organization > Screen configuration at the level of the organization or for individual sales channels.
- NEW V3.15 Define the time frame during which contacts can update ticket holder details.
- NEW V3.15 Changes in the prices of a price table used in an interface will pop up a warning message to ensure that this will not be breaking changes for the corresponding interface.
- NEW V3.15 When merging duplicates, the process will keep the most recently changed address even if the change was done on the "looser" contact ensuring that the most up-to-date address is kept.
- NEW V3.15 Thanks to a new batch you will be able to manage the cancellations in bulk with a dedicated batch in the context of the skidata-interface.
- NEW V3.15 When using the existing copy tariff feature, your operators will be able to include or not the custom variables linked to the copied tariff.
- NEW V3.15 Create a goods purchase order more easily by adding multiple goods items in one click.
- NEW V3.15 The ability for your customers to pay a part of a file or a part of their season ticket from their online personal space, an interesting feature that opens a new degree of flexibility.
- NEW V3.15 A new type of contact limit allows you to restrict quantities per product family or down to the activity level for events and competitions.