Technology Roadmap - Recent Threads

The Tessitura Community Sandbox is currently unavailable

Chris Hipschen — Fri, 27 Jan 2023 19:47:34 GMT

The Tessitura Community Sandbox is currently unavailable. We are conducting extensive system maintenance that will improve your Sandbox experience. We’ll post an update in the Technology Roadmap forum when we have an estimate of when it will be available again.

Tessitura Community Sandbox - v16.0.4

Chris Hipschen — Fri, 23 Dec 2022 17:00:52 GMT

Hello,

The Tessitura Community Sandbox is now on v16.0.4.

The community sandbox is a place for you to explore upcoming features of the Tessitura web application. All members of the Tessitura community are invited, and we encourage your participation and feedback. You can request access by emailing sandbox@tessituranetwork.com.

We hope you’re excited for the new features on the way in future v16 releases. To learn more, check out the v16 timeline, take a look at our roadmap, and subscribe to the roadmap forum to stay up to date.

For all of the latest innovation news, subscribe to product announcements. And you’re always welcome to join us for events.

Best,
Chris Hipschen
Director, Engineering Quality and Infrastructure
Tessitura Network

Tessitura Community Sandbox - v16.0.3

Chris Hipschen — Mon, 31 Oct 2022 14:21:46 GMT

Hello,

The Tessitura Community Sandbox is now on v16.0.3.

For all of the latest innovation news, subscribe to product announcements. And you’re always welcome to join us for events.

Best,

Chris Hipschen
Director, Engineering Quality and Infrastructure
Tessitura Network

Primary Addresses

Chuck Reif — Tue, 23 Feb 2010 16:36:37 GMT

One of our assumptions has been around the idea that a Next Generation constituent needn't necessarily have a postal address. As many of you know this requirement in the current software has caused us to jump through some hoops with web registrations where we actually temporarily create constituents with a dummy address. So the thought was if a large percentage of your constituents only address you electronically, why bother with a required postal address? Furthermore, considering the type of "groups with members" constituent model that we've been talking about, why should a every child in a family need an address when all of the children belong to a family that has a postal address?

So yesterday we got into having a big discussion about whether we needed to carry on the notion of a "primary address" for a constituent. Currently each constituent must have a primary address and that primary address must not be control grouped--everyone can see it.

Primary addresses has some nice advantages--if you want to analyze purchasing by postal code sometimes you just need any easy way to get to a postal code. Plus if you've got several addresses on a constituent and none of them really match the criteria for a particular mailing, you've always got the primary address to fall back on.

Obviously if no postal address is required then you can't force a primary address. You could make a rule like "if there are any addresses, then one of them must be primary". But then we thought, "does this work in a consortium setting"? Let's say the Symphony and the Ballet share a system. Couldn't you make the case that the Symphony might want to store a private address that only the Symphony could see? And that's the only address the constituent has on file? You can't say it's the primary address because the Ballet can't see it.

So several questions:

1. What about this notion of a constituent with no postal address? Does that make sense? Or does the current model feel better? Even with the group/member model we could say that each constituent has to have a primary address, even if that address is not specifically tied to that constituent. That's the example of the child's primary address actually being the family's address.

2. If there were no requirement for a postal address, then there are obviously still times when one is required. We couldn't have a delivery method of "Mail" if the constituent didn't have an address. Of course we could require that an order have a shipping address before allowing that delivery method. But what does this do to subscribers if some percentage of subscribers didn't have postal addresses? Or is this just the way the world is going and we have to learn to operate that way?

3. If we don't require an address, what about a primary flag? Is it ok for a constituent to have say 3 addresses (some shared, some not) and none of them being a primary address? Is it ok for a constituent to have 3 addresses, all only visible for some part of a consortium?

Believe me it's a nice feeling knowing that we can put questions like this in front a large, interested audience. We're eagerly awaiting your help.

RE: Primary Addresses

Kristin Nyquist — Thu, 20 Oct 2022 16:16:28 GMT

[quote userid="2411" url="~/tessitura_software_forums/f/tessitura_next_generation-0/2046/primary-addresses"]You could make a rule like "if there are any addresses, then one of them must be primary". [/quote]

I'm curious if this exact rule can be applied to email addresses. Has anyone had success with this?

Tessitura community sandbox changes

Chris Hipschen — Fri, 16 Sep 2022 17:56:23 GMT

Hello, current and future Tessitura sandbox users!

We wanted to let you know about some recent changes we’ve made to our sandboxes.

Version 16 includes many new features and enhancements. As we develop new features, you can experience them in the v16 sandbox. Moving forward, all new features will be browser-based. Therefore, the v16 Sandbox instance will only include access to the web application. This will give you the best Tessitura v16 experience. The v16 desktop application will no longer be accessible by Remote Desktop Connection.

Alongside these changes to the v16 sandbox, we have retired the v15 sandbox.

If you share a sandbox login with colleagues, please be sure to pass along this information to them.

For all of the latest innovation news, subscribe to product announcements. And you’re always welcome to join us for events.

Best,

Chris Hipschen
Director, Engineering Quality and Infrastructure
Tessitura Network

v16 Sandbox is available

Chris Szalaj — Tue, 01 Dec 2020 21:50:37 GMT

Hi everyone,

As announced on one of our recent Open Studios, the v16 Sandbox is now available. We regularly update the sandbox with our most recent progress on v16, so that you can explore the new screens and experience the new functionality first-hand that you see demonstrated in presentations.

For access:

Require new access?: email sandbox@tessituranetwork.com
Have existing sandbox access?: Use the same info you have already, include your sign in credentials and Remote Desktop URL.
Forgot your access?: email sandbox@tessituranetwork.com

Once you have requested access you will receive an email that details how to sign in and access the sandbox resources.

Thanks!

Chris Szalaj

Product Owner, Business Facing Products

Tessitura Network

RE: v16 Sandbox is available

Chris Szalaj — Wed, 14 Sep 2022 15:51:45 GMT

Hi Joyce Rudyanto, There are several orders on the Osborn family record: https://sandbox16.tessituranetworkdev.com/tessitura/#/crm/constituents/1006/orders

And you should be able to use those to render HTML templates in the HTML templates area of the application.

Thanks,

Chris

RE: v16 Sandbox is available

Joyce Rudyanto — Tue, 13 Sep 2022 19:28:02 GMT

Are there any sandbox order numbers that we can use to render the HTML templates in sandbox? I'd love to see how they render. Thanks!

RE: Printable version of the entire "what's new in v 16"?

Heather Fails — Tue, 22 Feb 2022 20:53:37 GMT

Thank you though!

Printable version of the entire "what's new in v 16"?

Heather Fails — Tue, 22 Feb 2022 20:13:46 GMT

Hi all. Call me old school (and a tree killer), I like to print the "what's new in v.." entire document, get out my highlighters and get to work. I can't seem to find how or where I can download the full enchilada to do so. Is this even a thing anymore?

Thanks,

Heather

RE: Printable version of the entire "what's new in v 16"?

Kanani Reichlin — Tue, 22 Feb 2022 20:52:40 GMT

oops just read the headline, v16... might not be created yet.

RE: Printable version of the entire "what's new in v 16"?

Kanani Reichlin — Tue, 22 Feb 2022 20:51:24 GMT

You can find them here, but they don't do them for service packs, I don't think.

www.tessituranetwork.com/.../Tessitura-v15_1

RE: Printable version of the entire "what's new in v 16"?

Heather Fails — Tue, 22 Feb 2022 20:29:12 GMT

Thanks, thought I'd give it a try.

RE: Printable version of the entire "what's new in v 16"?

Michele Keutsch — Tue, 22 Feb 2022 20:16:56 GMT

Me too! But alas I think this is a thing of the past.

December 2021 Tessitura Service Pack Now Available

Alex Harris — Thu, 16 Dec 2021 17:24:16 GMT

Hi everyone,

I'm pleased to share that the December service pack, 15.1.24, is now available. Highlights of this service pack include enhancements to the Payment Gateway Activity Log and the Event Cancellation Utility. Please see the product announcement for details and for the full release notes.

As a reminder: while we remain focused on releasing Version 16, we'll be releasing service packs for Version 15.1 only as needed. Details on the Version 16 scope and timeline, as well as preliminary documentation and training materials, are always updated on the Tessitura Version 16 Hub.

Best,

Alex Harris
Product Owner
Tessitura Network

tentative v16 release date?

Kathleen Smith — Mon, 22 Nov 2021 18:50:12 GMT

Hi all,

Is there any update on a (tentative, even) release date for v16? The latest I've heard is "early 2022", but am not sure if that means closer to January or April, or if it looks like there might be a different time entirely? I'm thinking about my timelines for next year, and having more of an idea when v16 is coming would be so helpful!

Thanks,
Kathleen

RE: tentative v16 release date?

Alex Harris — Mon, 06 Dec 2021 18:56:11 GMT

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

RE: tentative v16 release date?

James Ralph — Sun, 05 Dec 2021 15:19:42 GMT

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

RE: tentative v16 release date?

James Ralph — Fri, 03 Dec 2021 22:27:17 GMT

Hey Alex,

I did puzzle out that the out-of-the-box web header didn’t provide for a way to get our custom header info in place and wondered on first glance if the flex header would allow for that…or if there is an API I can hook into.

I’ll look at this and get back to you.

Thanks!

Jim

James I. Ralph, Executive Director

The John G. Shedd Institute for the Arts

868 High St - PO Box 1497 Eugene OR 97440

541.434.7001 – jqr@theshedd.net

RE: tentative v16 release date?

Alex Harris — Fri, 03 Dec 2021 22:15:35 GMT

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

RE: tentative v16 release date?

Rachel Walker — Wed, 01 Dec 2021 09:41:01 GMT

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

Best, Rachel

RE: tentative v16 release date?

James Ralph — Wed, 01 Dec 2021 02:39:07 GMT

Alex,

Our main concern is that we’ve invested quite bit in developing an effective Tessitura desktop user header interface for our ticket office & development staff which gives them immediate visual access to customer attributes/properties upon which they rely heavily. We are not able to discern the future of this InfoMaker-based Tessitura desktop app. Focus seems on the web interface. All well and good…but we really, really would hurt if the existing desktop interface is in any way deprecated.

Can you advise.

Jim

James I. Ralph, Executive Director

The John G. Shedd Institute for the Arts

868 High St - PO Box 1497 Eugene OR 97440

541.434.7001 – jqr@theshedd.net

RE: tentative v16 release date?

Chris Jensen — Tue, 30 Nov 2021 18:34:49 GMT

[quote userid="3222" url="~/tessitura_software_forums/f/tessitura_next_generation-0/29072/tentative-v16-release-date/78176#78176"]We previewed the feature in the Open Studio last March.[/quote]

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.

RE: tentative v16 release date?

Alex Harris — Tue, 30 Nov 2021 17:58:38 GMT

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