tentative v16 release date?

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

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