iticket
Menu
Unlock you potential

What's new in iTicket - October 09-10-2024

New Feature: Resource specification per event

We’ve introduced a new feature that provides an at-a-glance overview of resources associated with an event. This feature provides:

• Capacity Progress Bar Hover: When you hover over the capacity progress bar for any event, you’ll now see a detailed breakdown of available (free) vs. reserved (occupied) slots or seats for that events resources.

This enhancement allows for better visibility and management of event resources, enabling quicker decision-making and more efficient allocation of available seats or slots.

tooltips

New Feature: Enhanced List Filtering

We’ve completely revamped the list filtering experience in the Portal to make it more intuitive and efficient. This feature provides:

• Filter Count Display: The filter button now shows the number of applied filters, giving you a quick overview of your current filter setup.

• Overlay Filter Menu: Filters now appear as an overlay instead of a fixed panel, maximizing the visible space for the list you’re working with and allowing for a more streamlined interaction with your data.

This update simplifies list management and improves the overall user experience by offering a cleaner, more focused interface.

filter

(Not ready yet, but will be soon) New Feature: Apple Wallet support for Season Passes (Beta)

  • It is now possible to enable Apple Wallet for season passes. Please contact us if you want to activate this feature.

iTicket Booking Engine

  • We can now display a discounted amount ("You save") on add-on articles. (ID: 38914)
  • We have improved the display of campaigns on Sales and Distribution -> Channels. (ID: 40682)
  • We have added the agent and group reference to the printed version of order proof-of-value tickets. (ID: 42022)
  • We have created a date-range picker. We will roll it out in appropriate places over the next view months. (ID: 42421)
  • We are now automatically changing all characters used as tour code to uppercase characters in event types. (ID: 42651)
  • Further Swedish translations have been added to the iTicket portal. (ID: 42695)

Financials & Reporting

  • It is now possible to manually create and trigger a posting for Financials. (ID: 42801)
  • It is now possible to trigger revenue when values expire. (ID: 42085)
  • We have added the personal stock's validity date as a data source in reports. (ID: 42079)
  • We have changed the date and time on the voucher panel and export to be displayed in inventory time zone. (ID: 42269)

API

  • We have added orderCreationDateUTC and latestOrderVersion to the statistics API. (ID: 42400)
  • We are now exposing the customer language in customer/v1/customer and statistics/v1/orders. (ID: 42060)

Bug Fixes

  • We fixed a insights widget where the number of participants was displayed as negative numbers. (ID: 33805)
  • We fixed an issue where the amount of a refund of a redeemed voucher was shown on a previous order version. (ID: 41356)
  • We fixed optional complements information not transferring into iTicket (on both the order and the manifest). (ID: 41606)
  • We fixed an issue where the pricelist information was missing on the iTicket sales reports. (ID: 41622)
  • When an order does not produce a ticket (e.g. if there is no ticketing rule), we are now not displaying the "show tickets" button in the confirmation email anymore. (ID: 41811)
  • We fixed an issue where changing a booking retroactively removes usages & timestamps. (ID: 42493)
  • We fixed an issue where in certain cases "No proof of value found with provided identifier" appeared when opening a season pass. (ID: 42584)
  • We fixed an issue with event types for multi-activity resources, where we displayed locations instead of resources. (ID: 42586)
  • We fixed a permission issue for tag management in the portal. Users now need the inventory:inventory:manage permission to edit tags under tag management. (ID: 42738)
  • We fixed an issue with booking flow for transportation products that occured when using multiple add-ons. (ID: 42742)
  • We fixed an issue that occurred when you had more than one add-on in a BookingFlow product and the customer changed the route during booking.