7.35.2 Deployed to all LIVE Sites in the European Union

The 7.35.2 release has been deployed to all TNEW Live Sites in the European Union.

For v7, fixes and enhancements were released including those outlined below. This is not a complete list. The full list of enhancements and fixes included in this update is published in the v7 release notes section of the v7 TN Express Web User Guide. 

For organizations already using Third-Party Hosted Payments: You should update your TNEW Generic Hosted Payment method in TEST and LIVE to have Use With Card Reader checked to prevent missing refunds from not reflecting in Tessitura.

  • New Features

    • Specific Card Type Reporting: For organizations using Third-Party Hosted Payments, reporting of the specific card type used by a customer for the payment can now be reflected in Tessitura.  For more details, please see documentation in our help system. Instructions for configuring this feature are available in the TNEW Help System.

  • Small enhancements:

    • Synchronization of TNEW Product Type Editor and Product Editor Data: Prior to this release, changes to a Production Season or Performance Type for Performances in Tessitura were not synchronized with TNEW. Synchronization is now configured to occur regularly at five-minute intervals.

  • Fixes to reported defects

    • Refund Prior Payments:

      • When cancelling a refund prior payment for a payment made in TNEW, the action previously resulted in the customer receiving a refund through the payment processor that is not reflected in Tessitura.

    • Guest Checkout:

      • If the default shipping method for a mode of sale requires an address (“Require Address” in TR_ORDER_SHIP_METHOD), guest checkout would fail if the guest account did not require an address.

      • For members who are self-hosted, saving session variables twice may have prevented customers from successfully completing an order. Session variables are now only saved a single time for performance improvements.

    • Return Request Form:

      • In certain situations, submitting a return request would generate two Customer Service Issues (CSIs) for the request. A single CSI will only be generated when a customer uses the Return Request form.