Booker25 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.

Shared or Single Conflict checking?

Booker25 can handle conflict checking in two different ways.

1. Consider every dimension field/junctions as separate for conflict checking

2. Consider all dimension fields/junctions inside a dimension as a single dimension (Default)

You can switch between the behaviours using the Use Shared Conflict Checking checkbox on the Dimension object.

Practical example

In a clean Booker25 installation a dimension field B25__Contact__c and a dimension junction B25__ReservationContact__c exist. The two distinguish themselves by having two different contact relations to the reservation. For example, you are using this system to create reservations with a primary contact from a customer (dimension field) and a list of guests (dimension junction).

When you use option 1, considering every dimension field and junction separately, a person can be the guest and the primary contact at the same time. The two reservations will not conflict.

Option 2, enabling shared conflict checker, is for most scenarios the more intuitive approach. In this case, no matter how the contact is added to the reservation, either as a guest or as an organiser, it would block the contact being booked in another way.

Things to look out for in the shared conflict checker.

When shared conflict checking is enabled, all fields and junctions under that dimension need to use the same conflict checking type. You can’t mix a field that uses hard double booking checking with a junction that uses soft double booking checking. You will get a warning when you try to enable shared conflict checking but not all the conflict checking types are the same. In other words, if you say that a contact cannot be double book this should be true for both the primary contact and the guests in a reservation.

All fields that use capacity checking also need to use the same capacity field for both the dimension field and the dimension junction.

Conflict Types

There are currently three types of conflicts that Booker25 can detect:

Conflict Handling

There are three ways Booker25 can handle a detected conflict when creating (or editing) a Reservation

Configuration

You can configure Booker25 to handle different types of conflicts in different ways. For example if you have Resources and Staff, you can configure the following scenario:

1. Staff can't be double booked

2. Staff can't be booked outside of their working hours

3. Resources however can be booked outside of their opening times, without a warning to the user

4. Exceeding a Resource's capacity will give the user a warning, but still allows the user to save the Reservation

In configuration, the above scenario can be achieved in the following way:

1. On the Staff Dimension Field, set 'Double Booking Checking' to Hard

2. On the Staff Dimension Field, set 'Availability Checking' to Hard (note: this is only possible if you have already entered a value in 'Availability Lookup' on the Dimension)

3. On the Resource Dimension Field, set 'Availability Checking' to None

4. On the Resource Dimension Field, set 'Capacity Checking' to Soft

For this last step (4.), you will also need to enter the API names of the two fields telling Booker25 which fields to compare with each other to detect if the capacity is exceeded.

1. For 'Reservation Quantity Field', enter the API name of a number field on Reservation, such as 'B25__Quantity__c'

2. For 'Dimension Capacity Field', enter the API name of a number field on Resource, such as 'B25__Capacity__c'

Exceptions

For Double Bookings and Capacity checking, you can configure exceptions to let some Reservations pass through validation that would otherwise result in a Soft or Hard conflict. Let's say you have a few Reservation Statuses that do not count towards Double Booking or Capacity checking. A Canceled reservation for example may have the capacity filled in, which should not be taken into account during Capacity checking. You can create an exception as follows:

1. Create a checkbox named Canceled__c on the Reservation Status object.

2. Set this to TRUE on the Canceled Reservation Status record

3. On the Dimension Field of the Dimension you are working with, set the following fields:

   1. For 'Reservation Allow Double Booking Field' enter the following value: B25__Reservation_Status__r.Canceled__c

   2. For 'Reservation Skip Capacity Check Field' enter the following value: B25__Reservation_Status__r.Canceled__c

Now, all the reservations with a Reservation Status that has the Canceled checkbox set to TRUE will no longer trigger these checks and can be saved normally.

Finally, for Double Bookings, you can also reference a checkbox on a related record, to indicate that the related record always allows Double Bookings. Let's say you have Resources with a checkbox Can_Be_Double_Booked__c set to TRUE, then you can configure the following on the Resource Dimension Field:

1. For 'Dimension Allow Double Booking' enter the following value: Can_Be_Double_Booked__c

Double Booking will now be allowed only for this Resource, even when the overall checking has been set to 'Hard'

Related articles

• Page:
  Conflict Checking
• Page:
  Displaying Dimension Junctions on the Reservation Form
• Page:
  Shared vs Unshared Conflict Checking