Is there a way to a hide source code that are exclusively created for the web?
The only option currently in place at the DSO are for those source codes created by our Development Department (Fundraising), but would like to hide ones created for the web also.
Hi Paula,
I may not be understanding the question correctly but if you create an "Outside" source code, name it then change the source type to "Inside" it will be active but wont show up in the available sources when clicking on the source chicklet in an order.
Yes – you understand my question correctly! Thanks very much – this will help with maintenance of source codes.
Paula Johnson Ticketing and Applications Coordinator Dallas Symphony Orchestra Morton H. Meyerson Symphony Center Patron Services Center 2301 Flora Street Dallas, Texas 75201 214-981-2920 - phone 214-692-5133 - fax PJohnson@DalSym.com www.dallassymphony.com "To entertain, inspire and change lives through musical excellence" Click Here To Buy Tickets
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Ryan Rowell Sent: Monday, June 08, 2009 1:37 PM To: Paula Johnson Subject: Re: [Tessitura Ticketing Forum] Hiding Source Codes
From: Paula Johnson <bounce-paulajohnson6572@tessituranetwork.com> Sent: 6/7/2009 1:10:44 PM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!
Great! It was a happy day when I found out about that little trick.
Cheers!
Is it also possible to restrict availability of certain source codes to user groups? For example we have an internal Contact Centre that are making new and renewal subscription calls from promoted lists and it would be great if only the Contact Centre user group, and not the Box Office user group can see these source codes for booking orders.
Thanks,
Duane
At the appeal level you could associate a control group which restricts the appeal’s sources to only user groups to which the control group is assigned.
______________________________________
Ryan Creps
Network Developer |Tessitura Network, Inc
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Duane Woods Sent: Monday, June 08, 2009 3:03 PM To: Ryan Creps Subject: Re: [Tessitura Ticketing Forum] RE: Hiding Source Codes
From: Ryan Rowell <bounce-ryanrowell5634@tessituranetwork.com> Sent: 6/8/2009 1:57:09 PM
No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.12.53/2156 - Release Date: 06/08/09 12:30:00
Hi Duane,
We preface all of our source codes with a one-letter indicator so the reps know to which area the source applies. So, we use:
B - Box Office
F - Fundraising
X - Do not use
Ryan and Michele,
Thanks for the suggestions. We have not used control groups as of yet, so this may be a good way to start implementing them. I do like the idea of coding the source codes too, so I'll have to see what works best for us.
We've always used codes as well but ours are a little more crazymainly to make it as foolproof as possible for the ticket officeWe have:
Ticket OfficeT - ticket office generalSUB - Subscription OnlyPC - Promo CodesGRP - Group Sales
DevoD - Development generalE - Elevated Events
OtherA - Admin (used for in-house trustee cultivation/solicitation)M - Mailing lists traded to others