16.0.2.7 Deployed to all Test Sites

The 16.0.2.7 release has been deployed to TNEW Test Sites. 


Please note that the 16.0.2.7 release includes all enhancements and fixes from the 16.0.2.0 release which was not deployed to Production sites.


TARGETED PRODUCTION RELEASE DATE: October 4, 2022

  • Small Enhancements

    • Hosted Payment Configuration: The TNEW Generic Hosted Payment Method ID, previously displayed on the Hosted Payment page in the Administration Site when configuring a Hosted Payment Provider, has been removed. The property previously controlled the selection of a Payment Method when a mnemonic for a payment could not be found. The selection of the Payment Method is now based on Payment Method configuration. (Note: Requires Tessitura v16.0.2+)

    • Windcave: For organizations using Windcave Hosted Payments, Address Verification Services (AVS) can now be configured to automatically decline payments when the AVS result indicates a payment may be fraudulent due to a mismatch in address values.

    • Per-Seat Fees in Flex Package Selections Mini-Cart: If a performance was configured with a per-seat fee, the fee would display in the performance information and ticket selector but was excluded from the subtotal shown in the mini-cart. The subtotal shown in the mini-cart now included per-seat fees, when configured.

    • Page Headings on Event/Item Detail pages: The Default Heading and Page Title for the Event/Item Detail page has been updated to be unique. The {:PerformanceName}, {:PerformanceDate}, and {:PerformanceTime} tokens can be used in the Heading and Meta Title Override properties to dynamically display the Event/Item information as a page heading. The default value for the Heading property has been updated to {:PerformanceName}, {:PerformanceDate} {:PerformanceTime}.

  • Fixes to Reported Defects

    • Specific Hosted Payment Method Reporting: Some payments may have incorrectly been attributed to the TNEW Generic Hosted Payment Method when a valid card mnemonic was returned by a hosted payment provider. This was caused by a caching issue which has been resolved.

    • Windcave: For organizations using Windcave Hosted Payments, customers may have had payments treated as a decline when the transaction status was not yet available. Transaction status checking will now retry up to three additional times before treating a payment as declined when a status is not yet available.

    • Worldpay: For organizations using Worldpay Hosted Payments, customers may have had payments treated as a decline due to an unexpected response from Worldpay containing invalid characters. This response is now handled and will be treated according to the response code.

    • Tessitura Merchant Services: For organizations using Tessitura Merchant Services, several defects have been resolved:

      • Multiple Payments: Some customers may have experienced multiple charges for the same order after pressing the Check Out button multiple times on the Payment Page.

      • Payment Form Display: The payment form may not have displayed on the payment page unless the Gift Certificate Redemption section was enabled.

      • Payment Plans: Some customers may have been unable to complete an order when using a payment plan.

      • Apple Pay: Some users may have received an error after completing a One-Page Giving transaction while the order was successful.

    • Performance Availability: Performance Availability Messaging, when enabled on the Production Season Overview page and Additional Events Selection on the Event/Item Detail page may have been out of date due to caching of availability. This has been resolved and performance availability should now reflect real-time or near-real-time availability.

    • Package Dates: For packages in the Asia Pacific region, dates may have incorrectly shown as a day forward in the range displayed on the Package Listing and Package Detail pages. This was due to a regional configuration which has been resolved.

    • Order Confirmation Emails: Several issues have been resolved with Order Confirmation Emails. (Note: These fixes apply to all TNEW Order Confirmation Emails, including those that have already been configured as a copy in HTML Templates):

      • Time Display: When the Time Displayed property was configured for a Performance Product, the time for the performance was always displayed in the Order Confirmation Email instead of conditionally, based on the property value.

      • Cart Alias for Contributions: When a Cart Alias is configured for a Contribution Product, it was is now displayed in Order Confirmation Emails

    • Help Links in the TNEW Administration Site: The "Help" menu option, displayed in the TNEW Administration Site now links to the v16 Help System.

    • Package Mode of Sale: When a package has been previously added to the cart and then removed, users may not have been able to purchase single tickets due to the mode of sale not shifting back to the default web mode of sale.

    • Special Seat Notification Plug-In:

      • Seats are now grouped by seat type when displayed on the Special Seat Notification page displayed before a user reaches the Cart Details page.

      • The Special Seat Notification Plug-In Messages reference table now has a description column which can be used to display an alternative aliased name for a seat type when a seat with that seat type is added to the cart

      • When using Reference Tables, the Special Seat Notification Plug-In Messages reference table now displays as the name for the LTR_TNEWCUSTOM_SPECIAL_SEAT_TYPE table.

      • The Continue Button and Back Button, displayed displayed on the Special Seat Notification page displayed before a user reaches the Cart Details page, are now prefaced by the appropriate above_continue_button and above_back_button text. The buttons are now separated by a pipe separator.

    • Automate Donation Ask Plug-In:

      • The Donation Ask Plug-In no longer displays on the payment page when the cart contains a contribution associated with a fund.

      • When a Fund is configured to not be used in Ticket Order Processing, the fund cannot be used as a fund for contributions made using the Automate Donation Ask Plug-In

  • Maintenance

    • General security and maintenance updates.

The full list of enhancements and fixes included in this update is published in the release notes section of the Help System.