Change Log - 13 March 2025

New Features

  • Enabled storing the current user's name and ID in season pass transactions, including revokes and activations. (ID: 45848)
  • Introduced transaction origin (such as API, portal, online) and location for purchase, activation, and (un)revokes of season passes. (ID: 45900)
  • Done some work required to reuse current check-in functionality to use for the new digital coupons concept, such as to aggregate the amount of coupons purchased. The new "Digital Coupon" concept will be announced separately later this year. (ID: 46028)
  • Developed new /statistics/v1/metadata endpoints to be able to get a list of products, articles, price lists, discounts, resources, tags, locations and registries. (ID: 46036)
  • Changed Apple Wallet type to Store Card for season passes. (ID: 46362)
  • Added new states to Proof-of-Values (POV), supporting Active, Expired, Blocked, and Revoked statuses. (ID: 46527)

Improvements

  • Translated certain validation messages, such as "External identifier already exists" to be displayed in Swedish and French. (ID: 41636)
  • Improved UI for retroactive changes to provide a faster user experience. (ID: 45564)
  • Updated ticketing rules to ensure the correct "max validity days" setting is taken into account when activating imported season passes. (ID: 46326)
  • Manifest notifications now hide headlines if the notification is not sent as an email. (ID: 46466)
  • Improved cancel order functionality in API v6 to ensure all bookings under an order are properly handled and that rollbacks from the CRS or external systems are performed properly. (ID: 46478)
  • Added additional validation to prevent assigning an external card number to a season pass that is equal to the public ID of another season pass. (ID: 46212)

Bug Fixes

  • Fixed an issue where the period pass sub-period was not working as expected. (ID: 43024)
  • Resolved an issue where season pass articles to unlock campaigns could only be used in one campaign, even when the validity time was not overlapping. (ID: 44139)
  • Corrected calculations for the amount of campaigns applied in certain cases. (ID: 44158)
  • Fixed an issue where exclusive allotment was not releasing capacity back to common availability. (ID: 46065)
  • Resolved an issue allowing single-use vouchers to be redeemed multiple times. (ID: 46075)
  • Fixed discrepancies between the season pass list view, detailed view, and exports. (ID: 46287)
  • Addressed discrepancies between the season pass export and the season pass report affecting periodization. (ID: 46375)
  • Resolved an issue where day journal filters in the iTicket portal did not function correctly. (ID: 46408)
  • Fixed an issue where force-checkin did not work when performing check-ins using a POV. (ID: 46439)
  • Fixed price update issues in the widget when removing price groups. (ID: 46556)
  • Fixed a bug preventing booking of products with a pricelist tied to a season pass campaign. (ID: 46596)
  • Resolved an issue causing CheckinsV2 page to become unresponsive when applying filters. (ID: 46715)
  • Fixed an issue where it wasn't possible to unrevoke season passes. (ID: 41639)
  • Fixed an issue where the location was not saved when undoing pickups during a refund. (ID: 46470)
  • Resolved a bug preventing multiple articles from being added to a price section if an article was already listed. (ID: 46725)
  • Corrected an issue where the Easyrent pickup complement was not being transferred properly. (ID: 46764)
  • Fixed an issue causing problems when creating a new event type during event creation. (ID: 46800)
  • Resolved an issue where season passes incorrectly display the consumer as the owner. (ID: 46869)
  • Fixed an issue where page deletions with slots included where not deleted properly, leading to not bookable products. (ID: 46426)
  • Resolved an issue with times in transportation products that calculated the waiting time incorrectly, making it impossible to book certain round trip combinations. (ID: 46905)
  • Fixed a problem where payment transactions were displayed multiple times in the transaction log. (ID: 46915)