Hi,
As we explore and refine the potential architecture approach for the Next Generation product, a key element is extensibility. The current Tessitura software provides a variety of ways for organizations to extend the software today, and we have heard loud and clear that a high degree of customization/extensibility in the future product is a key requirement. One way to help us understand future extensibility needs is to first understand how you customize today. This is a purposefully open-ended question:
Please provide us with examples of customizations or extensions you have made to Tessitura and the business case behind why you made the extension.
We aren’t looking for every customization, but one or two samples that are either most representative or most difficult to accomplish in current Tessitura.
A quartet of examples:
1. We created a custom Box Office Statement in InfoMaker to match specific output field requirements of our promoter. This allows us to settle with the promoter in an efficient and speedy fashion, without us having to run multiple reports and combine them after the fact.
2. We adapted lp_customer_rank to automatically assign a constituency code of ‘Student’ if the constituent has purchased tickets to our Education season and has a customer type of Child. This allows CSRs to quickly identify students when looking up an account, and makes list pulling easier.
3. We created a custom constituent screen using InfoMaker to hold detailed information about our Press contacts. This allows us to have information about all constituents in one place, and ensures we can track specific seating assignments and preferences based on the reviewer.
4. We created a set of pages on our website to record individual member names on a family membership, tied to a custom table and custom membership card output so we can print individual member names on membership cards and link them back to a single membership in Tessitura. This means that multiple members of a household can each have their own personalized membership card while retaining a single membership on the household itself.
Thanks!
Andrew
Andrew,
Here are a few examples from City Opera:
1. Custom Screen designed to hold specific data for a specific moves management system recommended to us by an outside consultant. Basically the screen worked in conjunction with a solicitation record but contained more data (e.g. high, medium, low anticipated amounts, access, affinity etc.). It also contained some information from a wealth screening we did.
2. Customization to the header - to display the first line or so of text from a specific research note type we call "AAA". This could be anything super important that everyone in the company should be aware of when dealing with the constituent.
3. A Constituent report - accessed from within a specific constituent's record - (CONSITUENTS-CONSTITUENT REPORT) that gives detailed ticket information about that one constituent for the current season only.
Dale