Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Feature patch - Released in production the week 25-29.11.2021  

Status
subtletrue
titleUPCOMING

New features

New features delivered with the patch will be listed here soon.

Bug fixes

Bug fixes will be listed here one day before the release.27.10.2021  

New features

Online sales

  • The resale platform can now be used by customers using external managers (e.g. FortressGB)
  • Your season ticket holders can change the seat for all performances of their calculated season ticket in one step when buying online (if all performances in the season ticket share the same logical configuration and have the same seat category).
  • Injected TIXnGO tickets can be put on resale on the SecuTix resale platform in a secured way. Read more
  • (Tournament platform) In the lottery module, tickets sold within packages are now taken into account when computing global contact and match limits.
  • (Tournament platform) In the lottery module, category breakdown is now shown in the application summary for accessible ticket requests
  • (Tournament platform) When creating or managing group sales request online, your key clients can propagate the same quantities across all matches.

Back-office

  • The membership renewal batch is now able to renew automatically memberships valid for a fixed duration after purchase, no matter the duration of validity and season length. Read more
  • 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.
  • New search fields in the SecuTix back-office will let operators search for transactions by the last 4 digits of the credit card used for the transaction. Read more
  • SecuTix is now compliant with the TicketBAI regulation that will require each order to be digitally signed as of 01.01.2022. TicketBAI applies only in the Basque Country in Spain.
  • 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.

Engagement

  • DAN: Cultural contact dimensions are now available as filters and can be toggled in contact reports

Open Platform

  • New operator rights in virtual operator profiles can be used to control calls to some sensitive APIs (by default those actions will be allowed for virtual operators that are able to create orders already):
    • Sales interface>Refund order creation is required to create refund orders (ExternalOrderFacade.refundTicketOrder, ExternalOrderService.createRefundOperations)
    • Sales interface>Cancel reservations/options is required to create cancellation orders (ExternalOrderService.cancelOperations)
  • The reconciliation of sales between SecuTix and Skidata DTA can be performed using a dedicated batch

Bug fixes

  • [STX-114819] Item of the product service is not displayed in the personal ticket shop space
  • [STX-115778] It is not possible to return to the ticket shop beneficiaries input step and then continue the checkout
  • [STX-115838] It is not possible to modify ticket holders in the ticket shop after reset
  • [STX-115905] In some particular cases it is not possible to create/save any new entity in box office
  • [STX-116103] The total ticket number is incorrect in the lottery application emails
  • [STX-115708] Duplicate charges are applied for proximity payments

  • [STX-115401] Resume request submission in the lottery leads to an error

  • [STX-115718] In the ticket shop, the display is broken for the sessions of a season ticket

  • [STX-115777] Balance retrieved from Sports Alliance is not reintegrated correctly in SecuTix

  • [STX-115837] The "copy ticket holder data" checkbox in the ticket shop does not work correctly

  • [STX-115888] The advantages for parent contacts are not correctly assigned after merging with a child contact

  • [STX-115942] Companion seats are not selected properly

  • [STX-116201] Filtering of fields for access control API is not working


Expand
titleAdditional bug fixes
  • [STX-114591] Warnings on TIXAct comfort variable should not be displayed
  • [STX-115508] Incorrect order of packages is displayed in the ticket shop
  • [STX-115818] Contact webhook v3 displays a "+" in phone number when the field is empty
  • [STX-114186] Season card sale doesn't add all seats to the shopping cart
  • [STX-114658] Partial refund batch is resulting in error for tickets within packages
  • [STX-114696] An error happens in some screens when the operator has limited access rights
  • [STX-114874] Ticket holder data is editable when it should not
  • [STX-114967] Abandon file feature is not working correctly on exchange orders
  • [STX-115076] Customers should not be able to purchase two different categories within a package with category
  • [STX-115121] Goods item: weighted average without vat amount in CHF is sometimes rounded, sometimes not
  • [STX-115282] Shipments are marked as sent when there is an external error in the blockchain interface
  • [STX-115326] Ctrl-Click does not work from the installment screen to copy Slimpay reference
  • [STX-115335] 'Seat will be assigned later' text is not displayed for post seating
  • [STX-115436] It is not possible to modify row names when double clicking on a seat to edit
  • [STX-115465] Resale advantages are not visible in the dedicated screen when product family is automatically selected during creation
  • [STX-115467] It is not possible to logout properly when the customers ends up on an unauthorised lottery
  • [STX-115531] A technical error happens when trying to access the operator's cash desk
  • [STX-115539] The mobile account menu in the landing page does not correctly work when using a custom header
  • [STX-115575] Duplicate the cart pop-up is empty when logging in for the first time