How do you Extend Tessitura today?

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

Parents
  • Hi,

     

    1.Our Data Manager customized a report to group together different price types (Web Adult, Combo Adult, Adult) that have the same price point, for a given event. This enables us to sync our price typesthe daily reporting  requirements of attendance to the exhibition vendor.

    2. We are using the “Category” field of the order header to capture zip code information from walk-up, general admission patrons.

    3. Data from “Custom” tab fields is used to populate a custom calendar of daily group arrival times, number in the group, and leader contact information.

    4. We use a negative Payment Method to sell pre-numbered gift cards, and another to credit parking rebates to the order. We can track them on batch reports and the correct GL accounts are credited.

     

    Thanks, Andrew!

    Ray

     

     


    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Andrew Recinos
    Sent: Sunday, October 04, 2009 12:26 AM
    To: rbernard@smm.org
    Subject: [Tessitura Next Generation Forum] How do you Extend Tessitura today?

     

    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



    --
    View this message online at: http://www.tessituranetwork.com/COMMUNITY/forums/p/1290/4243.aspx#4243
    --
    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Reply
  • Hi,

     

    1.Our Data Manager customized a report to group together different price types (Web Adult, Combo Adult, Adult) that have the same price point, for a given event. This enables us to sync our price typesthe daily reporting  requirements of attendance to the exhibition vendor.

    2. We are using the “Category” field of the order header to capture zip code information from walk-up, general admission patrons.

    3. Data from “Custom” tab fields is used to populate a custom calendar of daily group arrival times, number in the group, and leader contact information.

    4. We use a negative Payment Method to sell pre-numbered gift cards, and another to credit parking rebates to the order. We can track them on batch reports and the correct GL accounts are credited.

     

    Thanks, Andrew!

    Ray

     

     


    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Andrew Recinos
    Sent: Sunday, October 04, 2009 12:26 AM
    To: rbernard@smm.org
    Subject: [Tessitura Next Generation Forum] How do you Extend Tessitura today?

     

    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



    --
    View this message online at: http://www.tessituranetwork.com/COMMUNITY/forums/p/1290/4243.aspx#4243
    --
    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Children
No Data