• Replies 19 replies
  • Subscribers 338 subscribers
  • Views 402 views
  • Users 0 members are here
Related

Examples of Custom Constituent Header Elements

Brian Parker (Past Member)
$organization

Good morning all,

I'm curious if anyone here would be willing to share some examples of information they've added to a Custom Constituent Header in Tessitura.

I'm currently in the process of thinking through some changes to our headers, and I've already written code to display an icon when a constituent has a gift they've made in the last week, as well as a modification to the baked-in Urgent CSI code so that it will display the icon if the constituent has an open CSI that isn't urgent.

Since I'm looking at this, I'm just really interested to hear other examples so that we can tackle a comprehensive overhaul if it warrants.

Thank you,

Brian

Parents
  • $organization

    Unknown said:

    I'm curious if anyone here would be willing to share some examples of information they've added to a Custom Constituent Header in Tessitura.

    We have lots of these. Some highlights:

    For Box Office:

     

    • The ever-popular "Next perf"
    • A header flag if the constituent has an open CSI
    • A different header flag if the constituent has an open Subscription-related CSI
    • A two more header flags that trigger if the constituent has a bad postal or e-mail address
    • We also append non-constituency "pseudo-constituencies" to the constituency string so that additional, short-lived codes representing redeemed staff comp purchases can appear in the header without the fuss of making actual constituencies for every production, every year. 

     

    For Volunteer admins:

     

    • Volunteer Reward points earned/used/redeemed

     

    For Devo:

     

    • Two for CY and Y1 AF giving totals
    • Communication preference
    • Expired, or no, CC on file

     

    Group Sales:

     

    • Group Sales code (a sort of category, school, business, etc.)
    • Primary Contact name

     

     

Reply
  • $organization

    Unknown said:

    I'm curious if anyone here would be willing to share some examples of information they've added to a Custom Constituent Header in Tessitura.

    We have lots of these. Some highlights:

    For Box Office:

     

    • The ever-popular "Next perf"
    • A header flag if the constituent has an open CSI
    • A different header flag if the constituent has an open Subscription-related CSI
    • A two more header flags that trigger if the constituent has a bad postal or e-mail address
    • We also append non-constituency "pseudo-constituencies" to the constituency string so that additional, short-lived codes representing redeemed staff comp purchases can appear in the header without the fuss of making actual constituencies for every production, every year. 

     

    For Volunteer admins:

     

    • Volunteer Reward points earned/used/redeemed

     

    For Devo:

     

    • Two for CY and Y1 AF giving totals
    • Communication preference
    • Expired, or no, CC on file

     

    Group Sales:

     

    • Group Sales code (a sort of category, school, business, etc.)
    • Primary Contact name

     

     

Children
  • $organization in reply to Chris Jensen

    Unknown said:

    For Volunteer admins:

    • Volunteer Reward points earned/used/redeemed

    Off-topic for a sec; we're in the early stages of developing a volunteer program, and I'd love to hear more details about this type of Volunteer Reward points system if at all possible!

    For Devo:

    • Expired, or no, CC on file

    Does this header element only trigger if there are no current credit cards on file? I'm curious about the code background on this; I'm assuming it's searching the cards to find a single record which has an expiration date greater than the current date and flagging if it fails to find one.

    Thank you for sharing!

    Brian

  • $organization in reply to Brian Parker (Past Member)

    Unknown said:

    For Volunteer admins:

    • Volunteer Reward points earned/used/redeemed

    Off-topic for a sec; we're in the early stages of developing a volunteer program, and I'd love to hear more details about this type of Volunteer Reward points system if at all possible!

    [/quote]

    A big customization involving both TNEW and Tessitura proper. The header displays points based on hours worked and rewards, i.e. comps, redeemed. I can elaborate further offline if you like. 

    Unknown said:

    For Devo:

    • Expired, or no, CC on file

    Does this header element only trigger if there are no current credit cards on file? I'm curious about the code background on this; I'm assuming it's searching the cards to find a single record which has an expiration date greater than the current date and flagging if it fails to find one.

    [/quote]

    This flag triggers if the patron has only an inactive CC, only an expired CC, and/or no CC.