GoMeddo can detect various conflicts that arise when Reservations are entered into the system. Furthermore, you can configure what happens when these conflicts are detected. This article explains the type of conflicts that can be detected, and all the configuration options for handling them.Info
Remove Double Booking permission from System Administrator profile
If you have enabled conflict checking but it does not seem to work, double-check if you have removed the Allow Double Booking permission from your profile, as described here: GoMeddo Clean Install| Note |
|---|
This article is about the older, well established dimension-based configuration. Recently, a new rule-based configuration has been introduced. Read about that here: Conflict Rules |
Conflict Types
There are currently three four types of conflicts that GoMeddo can detect:
Availability Conflicts | These happen when creating a Reservation outside of the defined Availabilities for a related record. For example, creating a reservation on a Friday for a staff member who only works Mondays through Thursdays. See this article for information on how to set up Availabilities for your Resources, Staff or other objects. |
|---|---|
Double Booking Conflicts | These happen when creating a Reservation for a record that is already occupied by another Reservation. For example, creating a Reservation from 8-11 and a Reservation from 9-12 in the same room |
Double Booking Matching Conditions | You can specify a condition that is applied to existing reservations in the database. Any existing reservations that do not match this condition are ignored and will not lead to double booking conflicts. An example of this would be making sure that two reservations in the same room have the same gender. This process is described on the following page. |
Capacity Conflicts | These happen when creating a Reservation that causes the related record's capacity to be exceeded. For example, creating a Reservation with 10 attendees in a room with a capacity of 6 |
Conflict Handling
There are three ways GoMeddo can handle a detected conflict when creating (or editing) a Reservation
None | Ignore the conflict, and don't notify the user. The Reservation will be saved normally |
|---|---|
Soft | Warn the user, but still allow them to save the Reservation into the system. A Conflict record will be created in the database so these problems can be solved at a later time |
Hard | Give the user an error, and do not allow the Reservation to be saved until the problem is solved |
Configuration Example
| Info |
|---|
The following assumes that you know how to configure dimensions, as explained in this article. |
...
Now all reservations with status cancelled can be booker booked even though there is no availability.
...
| Filter by label (Content by label) | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
|
...