Hello All,
I've gotten a few requests for files related to the Goodman's Mini Magic "Using SYOS to Sell Through Holds", so I posted them under my Community profile, as well as some other website controlling systems tables we have in place. The parent folder is Website Related System Tables. The sub-folders are Buying Through Holds, ADA, Hide Best Seat and SYOS, and Outside Productions. Buying Through Holds is related to our Mini Magic. It also includes files for the package version of buying through holds as well as single tickets which was the focus of our Mini Magic.
As I'm sure you know, these system tables and local procedures simply relay pertinent information to the website when they are called. A web developer will need to implement the appropriate calls and responses on your website for the tables to have any affect.
The major benefits of setting up system tables like these is that you can give control of your website functionality to your staff and reduce website developer maintenance. When your staff makes changes to the system tables your website responds almost immediately without getting your developer involved. Less $ spent on maintenance means more available for adding functionality and a quick turnaround means happy bosses and patrons.
Chris
I updated the stored procedure [LP_Web_Holds_Pkg], under Buying Through Holds,so it now verifies that all seats in a pkg have a proper primary/top hold. Now if a cover hold is placed on a seat of a performance within a package that seat will no longer be passed to the website for display in the package SYOS.
--U5. verify all seats in the pkg have a proper primary/top hold