Conflict checking
The content of this page is specific to the Delphi product type. If you are using the Delphi Core product type, click here to access the Delphi Core-specific online help.
Conflict checking ensures that multiple events are not blocked in the same function room at the same time. The following rules describe how conflict checking works:
- Conflict checking occurs when the booking event is saved.
- Conflict checking always occurs for tentative and definite booking events. However, your property configuration can also allow prospect events to hold space. In that case, conflict checking includes prospect events.
- When you try to block a booking event in an unavailable function room, your event is sent to the Unassigned function room. You can then modify the event by changing the function room or the start and end time to resolve the conflict. See Resolve booking event conflicts.
- Conflict notifications display on the booking event when setup and teardown times overlap with another event, or function room capacity requirements are not met. However, the event is not automatically moved to the Unassigned function room in these situations. You can decide whether the event can remain in the original function room.
- If part of a combination function room is already blocked, you cannot block that combination room. For example, the Ballroom is a combination of Salon A, Salon B, and Salon C. If Salon A is blocked, the Ballroom is not available for events on other bookings. Likewise, if the Ballroom is blocked, none of its component rooms are available.
Conflict checking exceptions
- Conflict checking does not include events on the same booking. For example, if you block an All-Day Meeting in Salon A from 8:00 AM - 5:00 PM, and you also block a Lunch in Salon A from 12:00 PM - 1:00 PM for the same booking, conflict checking is not required because both events are with the same customer.
- If the function room is a shared or common space, multiple groups are allowed in the space at the same time.
-