tentative v16 release date?

Hi Kathleen!

We're expecting to have more specific details soon, but we started our Version 16 Alpha testing process with a small group of organizations last month, and we are currently on schedule to start our Beta testing process for v16 in early 2022. Given the size of v16, we expect the Beta testing process to last at least 3 months. Since we'll be making final updates to v16 as we receive feedback during Beta testing, we are then expecting to be able to have the general release of v16 ready to go as soon as Beta testing is done. So we're currently projecting v16 to be in general release in Q2 2022.

We have lots of planning resources available on the v16 hub at https://www.tessituranetwork.com/en/Support/Documentation/Tessitura_v16. But if any questions come up that aren't answered there, please don't hesitate to send them our way.

Thanks!

Alex Harris
Product Owner
Tessitura Network

Hi, Also, it would be helpful to know what the estimated amount of work is for each organisation to move to v16?

Given the wide variance in organizations and their usage of Tessitura it would be impossible to calculate that across the board.

Hi James - the list of deprecated features in v16 is pretty short. And in every case for which we've deprecated a feature, it's been replaced with new or updated functionality to ensure that you've got a clear path from the v15.1 functionality to its equivalent in v16.

The full list of deprecated features in v16 can be found under the Scope tab on the v16 hub: https://www.tessituranetwork.com/Support/Documentation/Tessitura_v16. If you have any specific questions about deprecated features or their v16 equivalent, definitely don't hesitate to raise a support ticket.

Thanks!

Alex Harris
Product Owner
Tessitura Network

Alex Harris said:

The full list of deprecated features in v16 can be found under the Scope tab on the v16 hub:

There I see "QAS integration (This plug-in is being replaced with standard functionality using the newer Experian address verification)".

Is some part of Experian address verification slated to be built into v16? If yes, I must have missed that Open Studio session. :-)

Hi Rachel!

I'm happy to confirm Gawain's response. Since there's so much great new functionality in Version 16, it's hard to provide a single estimate that would apply broadly to every organization.

Where I'd probably encourage you to start your planning is in the What's New in v16.0 section on the website: https://www.tessituranetwork.com/Help_System_v160/Tessitura.htm#TN-Application/v16/Whats-New-Intro.htm. That provides a good overview of everything we've added in v16, and it should give you a feel for the functionality that will be most applicable to you.

As we get closer to general release, we will be providing lots of resources to help you prepare for and work through the upgrade process. In addition, we will be including an upgrade toolkit as part of the upgrade process. The toolkit provides you with an easy way to map any applicable data in v15.1 to its equivalent in v16, and to easily identify any customizations that might be affected by the upgrade. The toolkit and upgrade documentation are all part of our alpha and beta testing processes, and so they'll be well established when we get into general release.

Thanks!

Alex Harris
Product Owner
Tessitura Network

Hi Chris - and yes! We are working on an Experian address integration as part of v16. We previewed the feature in the Open Studio last March.

https://www.tessituranetwork.com/en/Items/Videos/Webinars/2021/Open-Studio-March-2021

Alex Harris said:

We previewed the feature in the Open Studio last March.

As I watch, I think I did attend that one, but the memory did not stick. Glad the integration is still coming, and looking forward to hearing more about the "new member pricing" mentioned in the Open Studio session above.

Hi Alex, Thanks for your reply. That's encouraging to hear about the toolkit.

Best, Rachel

Hi Jim - this is a great question. In v16, we have deprecated custom Infomaker headers on constituent records as we move towards a web interface; we did this to help ensure that constituent records fully match the new UI.

In doing so, though, we have expanded the functionality around flex headers--and we've tried to make sure to accommodate all of the most common requirements for which custom Infomaker headers are currently used. Full documentation on the new flex headers can be found here: https://www.tessituranetwork.com/Help_System_v160/Tessitura.htm#TN-Application/v16/Constituent-Header.htm.

As you look at the documentation, do you mind letting us know (product@tessituranetwork.com) if you find anything in your current custom header that wouldn't map cleanly to the new approach to headers? We're happy to help you work through any questions.

Thanks!

Alex
Product Owner
Tessitura Network

Alex, 

Thanks for getting back. From what I can see from the documentation at your proffered link (thanks!), the new constituent header is much more than a deprecation for my company: it will seriously undermine/hamstring our ticket office, development office customer service work flow and quality of service -- to the point that if I were considering buying into Tessitura at this juncture, I would need to look elsewhere. I know this is a radical, apparently histrionic thing to say, but this change isn't trivial.

Out-of-the-box, the Infomaker-based Tessitura client has always been a bit awkward, counter-intuitive, and conducive thereby to user (company staff) errors. The saving grace (and an important deal point in our decision to join the Network back at version 11, second only to Tessitura's significant database schema upgrade with that version) was the the ability to customize the client app's interface extensively. This has been especially important with respect to the almost completely customizable constituent header. We use this screen area extensively to get a wide range of critical-to-work-flow constituent information in front of our staff in an instant and easily-readable/recognizable format so that their ability to deal with clients on the fly is significantly enhanced. Losing this is a serious matter. Having traditional access to the Infomaker headers 

If we can customize the constituent header on our end, as we have with the Infomaker-based client, then we're whole. We have absolutely no problem with having to do that. However, if we cannot customize that header, that's a SERIOUS limitation. 

Does v16 provide for full customization functionality of its headers?

Jim

Hi Jim,

Thanks for the extra context - and thanks for sending all of the details of your current constituent headers to product@tessituranetwork.com. We're going to take a look at the details of the customizations you've put together, and we'll reach out directly via email to talk through how we anticipate you being able to use v16 without loss to your quality of service. As we look at the header together, it will also be helpful to look at the overall changes to the constituent records and the easier workflows that you'll have with v16.

We'll be in touch directly, and we look forward to working through the v16 upgrade with you!

Best,

Alex
Product Owner
Tessitura Network