v7.16.1 Deployed to all TEST sites

The 7.16.1 release has been deployed to all TNEW Test Sites.

For v6 & v7, the following updates were made to 7.16.0. The full list of fixes included in this update is published in the v6 release notes section of the v6 TN Express Web User Guide or v7 release notes section of the v7 TN Express Web User Guide. 

• Forgot Password Errors causing Email Addresses to be conveyed to Analytics: Updates to the application have been made to prevent conveyance of personally identifiable information via query string parameters that were occurring in the rare instances when the forgot password submission caused an error. We do recommend that you review your configuration of Google Analytics - specifically the Google Tag Manager - in order to intercept any personally identifiable information before it is ingested into Google Analytics.

For v7, the following updates were made to 7.16.0. The full list of fixes included in this update is published in the v6 release notes section of the v6 TN Express Web User Guide or v7 release notes section of the v7 TN Express Web User Guide. 

• SYOS: 7.16.0 introduced an issue with product type level and product level settings for enabling SYOS in that if the "TN_Express_SYOS" property existed in Web Content in Tessitura, it overrode the settings in product type editor and product editor causing some performances to have SYOS disabled. 

7.16.1 also includes all of the updates that were released in 7.16.0 as outlined below. 

For v6 & v7, the following updates were made. The full list of fixes included in this update is published in the v6 release notes section of the v6 TN Express Web User Guide or v7 release notes section of the v7 TN Express Web User Guide. 

• Payment Express Hosted Payments: While we recommend that FPRNs (Fail-proof result notification) be turned off for all integrations with Payment Express, we have also updated our hosted payment integrations to filter out any FRPN requests in order to avoid triggering any unexpected behavior that they may cause. 
• Waiting Room Admin: An "in-process" indicator has been added to the "Save" button in admin for Waiting Room configuration in order to provide indicator that the save is in process. 

For v7, additional fixes and enhancements were released including those outlined below. The full list of enhancements and fixes included in this update is published in the v7 release notessection of the v7 TN Express Web User Guide. 

• New enhancements:
  
  • Inactive Product Types: If a performance product type has been inactivated in Tessitura, the product type will now display in a new "inactive product type" section at the bottom of the product type editor with the list of inactive product types collapsed by default. 
  • Performance: Content for production seasons and performances has been separated from pricing and availability data on the listing/calendar page, events/detail pages and flex package pages in order to support different caching behaviors based on need. This allows content to be cached for longer periods of time (up to 60 minutes) while more real-time data regarding pricing and availability are cached for 20 seconds. In either case, if you need to see an update more immediate than these cache schedules, you can clear the cache in the admin tool. 
  • Facebook: TNEW has been updated to reference version 3.2 of the Facebook API. 
  • Manage Visibility of Performances on TNEW based on web publish dates: With the release of 7.16, you can now control whether or not a performance is "visible" on TNEW via web publish dates. If a performance has a web publish date that includes today's date range and/or does not have any web publish dates configured, they can be accessed on TNEW via direct URL (and/or on the listing/calendar page based on MOS and Keyword) regardless of the MOS. In order to have a performance not display or be accessible on TNEW, the web publish dates should be either set to the past or the future. NOTE: this applies to the TNEW application right now. Further updates will be made to the admin controls in a future release. 
    
    
• Fixes to reported defects:
  
  • Shared Session: After log out, the new session key is returned using the Get call instead of the old session key. 
  • Double Clicking Modals: If a user happens to double-click on a button or link that triggers a modal window, the modal now renders successfully and behaves as expected. 
  • Pricing Rule Messages: The Single Listing Message that should appear on the listing/calendar page was not appearing as expected. This has been fixed. 
  • Price Type Pricing based on Promotion Code: Changes in price type pricing based on promotion code was not displaying upon initial submit of the promo code but required a refresh of the page. This has been fixed. 
  • Contribution Types: If a contribution type had an non-editable suggested donation amount configured, the suggested amount was not appearing if the contribution group page had only one contribution type. This has been fixed. 
  • v6-to-v7 Redirects: The redirects from the v6 PSDetail.aspx page to the appropriate v7 events/detail page was not working as expected. This has been fixed. 
  • Pricing Rule configuration error causing generic error: If there was an issue with the pricing rule configuration (which uses REST) then the user would receive a generic error. This has been fixed. The user now will receive a more user-friendly error page. 
  • "Single Seats Enabled" in Flex Packages: The "Single Seats Enabled" property in the component editor for flex packages was not working as expected and causing an error when submitting request if Single Seats Enabled was set to true. This has been fixed. 
  • Select Your Own Seat (SYOS): If SYOS is enabled for a performance but an SYOS map is not available for some reason for said performance, the user will be automatically redirected to best available view instead of receiving an error. 
  • Abandon Cart Link Token: The "{AbandonCartLink}" token which is included in error messages like the "Promo Code Cart Conflict Message" and allows user to clear their cart by clicking on the link the contains that token was not working as expected. This has been fixed.