CASE User-Defined Ticket Elements

Is anyone currently using a conditional user-defined ticket design element? For example, when the zone is GA then GA else seat_no? Or any other...

Anyone ever run into issues with a conditional design element that I might be overlooking?

Parents
  • Is this even possible?  If so how do you set it up?  It is definitely something that would make some things much simpler, but I never saw a way to make it happen within Ticket Design.

  • I have one that we user for a ticket header for one of my groups that looks for the status codes of Name1 & 2.  For our Corporate tix this group likes to have our contact name be name 2 for routing purposes when mailing, but for a regular individual joint account if the Name 1 or 2 is deceased, well that would be bad.  I can send you the script if you like.

     

    MH


    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Boann Petersen
    Sent: Thursday, July 30, 2009 4:34 PM
    To: Matt Hilgers
    Subject: Re: [Tessitura Technical Forum] CASE User-Defined Ticket Elements

     

    Is this even possible?  If so how do you set it up?  It is definitely something that would make some things much simpler, but I never saw a way to make it happen within Ticket Design.

    From: Amanda Freeman <bounce-amandafreeman5080@tessituranetwork.com>
    Sent: 7/30/2009 1:03:44 PM

    Is anyone currently using a conditional user-defined ticket design element? For example, when the zone is GA then GA else seat_no? Or any other...

    Anyone ever run into issues with a conditional design element that I might be overlooking?




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply
  • I have one that we user for a ticket header for one of my groups that looks for the status codes of Name1 & 2.  For our Corporate tix this group likes to have our contact name be name 2 for routing purposes when mailing, but for a regular individual joint account if the Name 1 or 2 is deceased, well that would be bad.  I can send you the script if you like.

     

    MH


    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Boann Petersen
    Sent: Thursday, July 30, 2009 4:34 PM
    To: Matt Hilgers
    Subject: Re: [Tessitura Technical Forum] CASE User-Defined Ticket Elements

     

    Is this even possible?  If so how do you set it up?  It is definitely something that would make some things much simpler, but I never saw a way to make it happen within Ticket Design.

    From: Amanda Freeman <bounce-amandafreeman5080@tessituranetwork.com>
    Sent: 7/30/2009 1:03:44 PM

    Is anyone currently using a conditional user-defined ticket design element? For example, when the zone is GA then GA else seat_no? Or any other...

    Anyone ever run into issues with a conditional design element that I might be overlooking?




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Children
  • I guess I had never looked that closely at the user defined elements before!  I would love to see a sample of the script you use.  This opens up a whole new area of ideas for us!

  • Former Member
    Former Member $organization in reply to Boann Petersen

    We have a couple of custom ticket elements that we use:

    We look for the string "XX:" at the start of the order notes and take everything up to a semicolon as the will call name (using UD1) on ticket headers.  Otherwise we use N1 or N2 for the will call name (depending on the name format).

    If the price type is a Voucher price type, we print the word Voucher on the header (using UD2) so the box office clerks will collect the voucher from the patron.

    I have posted our lp_ticket_elements.sql in my files area if anyone wants to take a look at it.

     -steve carlock

    Santa Barbara Center for the Performing Arts/The Granada