Are you using any of the user-defined data elements on your ticket designs? I'm currently working on a new ticket design document and I'm looking for some practical examples of what data people are retrieving with these elements. If you are using them, please reply to this thread and share what data you are retrieving. No code from the stored procedure required, just which data you are printing on the tickets.
Thanks!
Hi Kevin,
Not sure how practical they are as they are pretty ACT specific but here are the ones we have
One to print the aisle number (kept in a custom table) for our theatre in the round.One to print a message when someones monthly ticket "membership" payments are late based on a constituency that is automatically maintained via sql job.(not to be confused with devo memberships)One to print number of parking sold in a package which prints on the header. (we print season tickets on normal ticket stock and have 3rd party parking vouchers)
I'm also going to be making one to print a message on the header for Will Call when an ID needs to be checked due to age discounts.