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
Here are a few of the ways we have extended Tessitura at Lyric: 1) Some of our Constituent custom screens are: Grant and proposal management - project, worker, status, ask amount, received amount, due dates (includes custom reporting and system tables) Donor dining room reservations, dinner orders and notes (includes custom reporting and system tables) Auction purchases - event, lot, price, value, taxes, paddle,donation amount (includes custom reporting and system tables) Donor Gifts - track gifts by item, date, reason and solicitor (custom system tables for donor items and reasons) 2) We use Ticketing Setup/Sales for the following 'other' items. All require custom reporting and most require custom system tables: Various merchandise and publications Backstage Tours including optional lunch choices Raffle Tickets Restaurant Reservations 3) Ticketing/Marketing Department Customization Custom capacity management report for subscription seating Use of email addresses for logins, custom procedures for soft/hard bounce management, assignment of temporary logins based on subscription order number Custom subscription acknowledgments,confirmations, receipts with individualized messages based on sub summary status and type Custom renewal forms with many different messages depending on package Order entry exception reports to find any operator errors 4) Development Department Customization Custom stored procedure to 'rollover/create' solicitations for the following year
Here are a few of the ways we have extended Tessitura at Lyric:
1) Some of our Constituent custom screens are:
Grant and proposal management - project, worker, status, ask amount, received amount, due dates (includes custom reporting and system tables)
Donor dining room reservations, dinner orders and notes (includes custom reporting and system tables)
Auction purchases - event, lot, price, value, taxes, paddle,donation amount (includes custom reporting and system tables)
Donor Gifts - track gifts by item, date, reason and solicitor (custom system tables for donor items and reasons)
2) We use Ticketing Setup/Sales for the following 'other' items. All require custom reporting and most require custom system tables:
Various merchandise and publications
Backstage Tours including optional lunch choices
Raffle Tickets
Restaurant Reservations
3) Ticketing/Marketing Department Customization
Custom capacity management report for subscription seating
Use of email addresses for logins, custom procedures for soft/hard bounce management, assignment of temporary logins based on subscription order number
Custom subscription acknowledgments,confirmations, receipts with individualized messages based on sub summary status and type
Custom renewal forms with many different messages depending on package
Order entry exception reports to find any operator errors 4) Development Department Customization
4) Development Department Customization
Custom stored procedure to 'rollover/create' solicitations for the following year
Two more from Lyric Opera of Chicago: We set up custom messaging by series on our renewal form. If a series is discontinued or if the patron bought a non-renewable series we have a custom renewal form report to generate renewal bills. We use price types to calculate subscription ticket exchanges on the single ticket value rather than the subscription discount value of the ticket. We use a custom field on each performance date to list the series & price type "exchange codes" that are possible, and pull that data into a ticket design element for the subscription ticket print.
Two more from Lyric Opera of Chicago:
We set up custom messaging by series on our renewal form. If a series is discontinued or if the patron bought a non-renewable series we have a custom renewal form report to generate renewal bills.
We use price types to calculate subscription ticket exchanges on the single ticket value rather than the subscription discount value of the ticket. We use a custom field on each performance date to list the series & price type "exchange codes" that are possible, and pull that data into a ticket design element for the subscription ticket print.