Change Log - February 2025 13-02-2025

New Features

  • The campaign type "One-time use codes" is now called "Multiple Unlock Codes" and has additional functionality. It is now possible to create multiple unlock codes that can be used more than one time each. Your existing one-time use codes have been changed to "multiple unlock codes" and we have added a restriction of 1 maximum booking per code to ensure those unlock codes can still only be used one time.  (ID: 45612)
  • New permissions have been added to gain read or manage rights for Season Passes and Vouchers. Users without the "read" permission for Season Passes or Vouchers won't see the respective panels in the portal. (ID: 45582)
  • Introduced a new permission ("users:manage-limited") to allow non-admin users to only create users within the same user group. (ID: 45568)
  • Introduced a new campaign validation service to ensure usage restrictions are validated during price search and not just at the add-to-cart stage. (ID: 40497)
  • Added "register groups" as a new data source for enhanced reporting capabilities. (ID: 44640)
  • Added "FirstCheckin" as a column in the season pass export. (ID: 45570)
  • Integrated "FirstCheckin" as a data source in reports to allow for detailed analytics. (ID: 45573)
  • Introduced new "Manage" and "Read" permissions for value vouchers and Season Passes on the iTicket portal.
  • It is now possible to do Enter and UndoEnter operations using grouped tickets ("ticketGroupValue").
  • Added an additional filter to the season pass panel to filter for the issue date of season passes. (ID: 45925)

Improvements

  • Updated Swedish translations across the platform for consistency. (ID: 42695)

Bug Fixes

  • Fixed an issue where one-time use codes could be used multiple times within the same order. (ID: 38693)
  • Fixed an issue where the activation link for season passes did not work for the second and following season passes when more than one season pass was sold in an order. (ID: 45795)
  • Resolved an issue where the calendar incorrectly displayed days as bookable when only an add-on has a valid price but the mandatory product lacks one. (ID: 44503)
  • Fixed booking failures when multiple events at different locations had one fully booked event. (ID: 44506)
  • Addressed the issue of optional complements not showing in manifests or order views. (ID: 44777)
  • Corrected an error that was thrown when using "capacity override" when editing an order that has exceeded capacity. (ID: 45106)
  • Resolved an issue with exclusive allotments where the release option in certain cases released other tours than today's tour. (ID: 45142)
  • Fixed a "sold out" error for exclusive allotments where there is remaining capacity. (ID: 45317)
  • Corrected booking date start time in iTicket price lists to use the inventory time zone instead of UTC. (ID: 45352)
  • Fixed an issue where users could not access manifests even though the inventory:manifests:view permission was granted. (ID: 45519)
  • Resolved an issue where undoing a check-in corrupted an order and made it inaccessible in both POS and the portal. (ID: 45546)
  • Addressed an issue preventing changes to events in iTicket. (ID: 45808)