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
Hi Andrew,
Good day.
we customized sponsorship custom screen, packeage & price type reports, daily sales reports, hold code reports, contact management custom screen.
In Tessitura point view, customization can be separated into two parts, custom screen and custom report.
I'd like to separate customization into loose binding and tight binding.
because any kinds of appliactions, can be separated into two parts: data and user interface. if your customization binds data and interface with Tessitura, that is a tight binding, if you only pick up data, that is a loose binding.
I prefer to go with loose binding, I can copy the system data to somewhere else, do my job, then show them in a report or a custom screen. because I only use the data, I have the same privilege as Tessitura. these are sales reports, hold code reports, package & pricetype reports.
1, tight binding:
Of course, we have a tight binding example, which is the sponsorship custom screen. I was asked to share this custom screen, but I almost cannot do so. It tights up with tr_tkw, tr_tkw_catgory, tables in the season setup, and other custom tables. When new season comes, then bugs come, dozen of places need to be updated. I cleaned up half of those, now we have a reporting service report can export Excel files from cross-tab reports. I am thinking of redesign it to make things simple and clean, but I haven't get the permission yet.
2, half loose binding:
for the contact management custom screen, it took me quite a lot of time to build, as I was a novice of Infobreaker. Finally we chose CSI to update the custom screen, custom screen itself is for display only. I think IM is a good boy, and display info only is the best job for this good boy. And it works perfectly, no errors, no troubles.
3, loose binding:
A,
For the sales reports, I simply don't trust a summary report without detail. So DIY.
B,
For hold code reports, we have ticketMaster sales need to be counted. Email-->SSIS--> scheduled reports.
C,
Constituency customization is a real challenge. This part of code adds constituency A on, that part of code drops constituency B off. At last, we have a long list to take care. I am thinking maybe we need something else to make this better.
Thank you for your time.
have fun
Ben