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
Unknown said: For Volunteer admins: Volunteer Reward points earned/used/redeemed
For Volunteer admins:
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
For Devo:
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.
This flag triggers if the patron has only an inactive CC, only an expired CC, and/or no CC.
Unknown said: For all users: We have a Development Staff Liaison attribute that shows up in the header, if it exists.
Lucie,
So this displays out the name of a Development staff employee who is specifically connected to a patron via attributes; very cool. Right now only our Development and Education team members are in Tess, but I think it'd even be a nice thing to have so that Education members know who to refer constituents to for Development needs.
Thank you for sharing!
Unknown said: For our Customer Facing staff (Call Center, Box Office, Front of House, etc): - Member Notes (brief description of benefits) For our Development staff sees all of the above, plus: - Entity Affiliation - the organization/corporation an individual is affiliated with. A string of names if the individual is affiliated with multiple organizations
For our Customer Facing staff (Call Center, Box Office, Front of House, etc):
- Member Notes (brief description of benefits)
For our Development staff sees all of the above, plus:
- Entity Affiliation - the organization/corporation an individual is affiliated with. A string of names if the individual is affiliated with multiple organizations
Frances,
Are you displaying the Member Notes and Entity Affiliation directly on the constituent header or as a mouseover? Just curious because, thinking in terms of our own benefits and data, it would take a significant amount of space in our headers to display the same.
Hi Brian,
In terms of member notes, it's actually very brief so we are including it in the header. We have a lot of similarly named member programs - for instance three different types of members: Premium, Preview, and regular. Since some ticket access does depend on this , we didn't feel the 3-character description was enough and so we describe the member category in the header - that's what I mean by member notes. Let me know if I can describe further.
And we do list the entire entity affiliation, although this is a little more self-explanatory. Only caveat is we only list certain entity affiliation types - basically it only shows up if the constituent is an affiliate with type of Trustee - so the string isn't usually too long to show up.
happy to clarify further - let me know!