Restriction Types |
Top Previous Next |
There are several different pre-defined Restriction Types, allowing for a variety of basic validation criteria. You can have as many different restrictions of each type as you like. While these types cannot be changed, the "Applies only to" conditions of the Restriction Definition allow a lot of flexibility, including a fully programmable "Condition expression" -- essentially allowing limitless flexibility in the types of restrictions you can create.
Remember that the Type is only one part of the definition -- in order for the reservation to be restricted and/or the warning shown, it must also meet all of the conditions specified in the "Applies only to..." section of the definition.
Always, if applies to reservation -- This is a generic restriction, which means trigger for any reservation meeting the defined conditions. So if you can define the conditions of the restriction in the "Applies only to..." section, then simply select this type to restrict all reservations with those conditions. An example would be not allowing a Monthly reservation in a Cabin -- select "Monthly" for the Resv Type and "Cabins" for the Site type, and select this Type to not allow that combination.
Minimum days long / Maximum days long -- Don't allow a reservation shorter or longer than the # days specified. (In most cases you could also use the "Applies if >= days / <= days" to do the same thing, but there are certain combinations that having this as the Type can help with.)
Maximum consecutive days -- This is much more powerful than the simple "Maximum days long" type -- this will look at all other reservations for the same customer, on any site, and sets a limit on the consecutive number of days in the park. So if you want to make sure they're not site-hopping to try to avoid the limitation on days-in-a-row they can be in the park, use this type instead of "Maximum days long".
Maximum concurrent reservations -- This limits how many reservations they can have overlapping on the same date (for instance to prevent a member from making a reservation for a friend under the same name).
Minimum days out -- This sets a requirement that they not have any 2 reservations closer together than the given number of days. By using this and also a restriction of "Maximum consecutive days", you can easily implement a rule like "Max 14 days per stay with at least 7 days in between stays".
Maximum days in the calendar year -- This sets a limit on how many days the customer can be in the park in a given calendar year. Note that his is pre-defined as January 1st to December 31st, it cannot be an arbitrary time frame.
Maximum reservations in the calendar year -- As above, but limits the number of separate reservations in a year.
Maximum days in the calendar month -- This sets a limit on how many days the customer can be in the park in a given calendar month.
Maximum reservations in the calendar month -- As above, but limits the number of separate reservations in a month.
Maximum days in a given time span -- This sets a limit on how many days the customer can be in the park in a given time span (number of days), for instance a limit of 14 days within any 30-day span.
Maximum reservations in a given time span -- Similar to "Maximum days in a given time span", but this only counts unique reservations. This would be limited usefulness of course unless you also have minimum reservation lengths, or just want to limit how many times they change sites (requiring separate reservations).
Maximum total days on certain dates -- This limits the total number of days on certain specified dates. This can be a date range (e.g. your season), or any combination of date ranges (e.g. to limit their total nights on all holidays for the year).
Maximum reservations on certain dates -- As above, counts the number of separate reservations that have at least one day covering the dates you specify, rather than the total nights on those dates.
Must include a minimum # of certain dates -- This can be useful in certain special cases, for example if you have a 5-day special event and want to make sure that any reservation during the event includes all 5 days of the event, or at least 3 of its days, etc (e.g. to prevent someone just passing through from taking up a valuable site during the event).
Must not include more than # of certain dates -- This defines a maximum number of days that can be included within a certain time frame, in the single reservation. It does not prevent multiple reservations for the same customer from having a combined total more than the maximum days defined.
Maximum future days reserved -- Limits how many total days they have reservations for after today.
Maximum future reservations -- Limits how many total reservations they have reservations for after today.
Minimum # / Maximum # periods (hourly/schedules) -- These specifically apply to "Scheduled" reservations, e.g. for Hourly rentals. For instance, you can set a minimum or maximum number of hours that can be in one reservation.
Maximum consecutive periods -- This is much more powerful than the simple "Maximum # periods" type -- this will look at all other reservations for the same customer, on any site, and sets a limit on the consecutive number of periods reserved. So if you want to make sure they're not site-hopping to try to avoid the limitation on periods-in-a-row, use this type instead of "Maximum # periods".
Topics:
Restrictions & Reminders Overview