Hi, I thought I'd post this here rather than open a ticket, in case others wanted to chime in on whether it's something you would want as much as we do. Or possibly because someone here will know some option I'm missing that will allow me to do these things without hacks.
We book a handful of one-off general admission community events in our theater that is normally a reserved seat venue. In order to clean up the Event/Item Detail page in TNEW for these events, as the in-house web developer I am currently using a CSS hack to hide the zone selector section, since there's only one zone and no need to confuse people with this. It would be really cool for hiding this section to be an option in TNEW Admin.
It's true that we can hide the Best Available zone option, but I don't understand why Best Available would appear for an exclusively GA event anyway. But really, sometimes we just want to hide that whole section.
And along with this, I end up hiding the contiguous seats checkbox also, because again, this is irrelevant for a GA event.
I guess this is really two feature requests:
Thanks,Chris
Upon further thought, as someone who is more familiar with TNEW specifically and not as much how Tessitura needs to process things, I'm guessing this is complicated by the fact that a zone HAS to be selected in order to sell a seat. Even if the zone select section is hidden, the data for this field still needs to be sent to the API. Which is why hiding it with CSS works, since the selected input field still gets processed on submit. Whereas when things are "not displayed" by TNEW, they generally aren't to be found in the HTML output at all. That means the zone would have to be auto-selected by Tess behind the scenes somehow, probably requiring a bit more programming than I had initially considered. I still think it would be a convenient feature, though. :)And I still think it makes sense to exclude Best Available and Contiguous Seats when the only zone on sale is GA. Unless I'm missing something there?
I think this can be accomplished with just using a Zone Map with one zone. Since there is only one option for the zone, the zone selection button does not populate on TNEW. For example, this facility has two zone maps. One is a GA zone map where we don't care about limiting the number of tickets (we are a Zoo, so these are not seats). On TNEW, it skips the zone selection for performances with this zone map.The other zone map has 10 zones with 3,000 seats in each. We use this when we want to limit the number of tickets and that limit is > 3,000.We only have one Best Seat Map and GA Best Seat Map is selected on the facility.You could confirm this in your Test environment in an existing facility. Depending on how many facilities you already have, you could build a new facility just for this purpose. Although, just creating a new Zone Map is way faster.Does that make sense?
Hi Neil, thanks so much for your reply! Your idea certainly sounds like it makes sense to me, but I'm just not familiar enough with how our maps are set up in Tess. I'm going to forward this to my Patron Services and DBA folks, and see what they make of it. Thank you again!