Conflict handling is a key feature in any scheduling tool. It means that if an object is double booked the system can give a conflict alert. There are various related settings that can influence the behaviour and also when a conflict is created.
TABLE OF CONTENTS
- Object Cause Conflict
- Preliminary Bookings Cause Conflict
- Cancelled Bookings
- User Permission: User Cannot Book Conflicting Object
- Inspect
- Solving conflicts
Object Cause Conflict
An Object will ONLY cause a conflict alert IF the "Causes Conflict" is ticked. The option to turn off conflicts for an Object exists for all bookable Object Types.
The Booking Sub Status is key for the Conflict behaviour.
- A booking with Confirmed Sub Status over another Booking with Confirmed status WILL create a Conflict Warning on Objects that have the "Cause Conflict" set to yes.
- A booking with Preliminary/Planning Sub Status CAN create a Conflict Warning when making a double booking if the Toolbox > Setting > Server Setup > Preliminary Booking Causes Conflict Warning (applies to Planning too) = Yes.
- A booking with Cancelled Sub Status WILL NOT create a Conflict Warning when making a double/conflicting booking.
Preliminary Bookings Cause Conflict
A booking with Preliminary/Planning Sub Status CAN create a Conflict Warning when making a double booking if the Toolbox > Setting > Server Setup > Preliminary Booking Causes Conflict Warning (applies to Planning too) = Yes.
Cancelled Bookings
The cancelled booking sub-status will not cause a conflict in general.
Pre-conflict checker
If you create a Booking that would result in a Conflict, a Pre-Conflict Message appears. With this user setting turned off, when you create a Booking that would result in a Conflict you will straight get the Conflict window showing the conflicting Booking(s).
User Permission: User Cannot Book Conflicting Object
Allows you to control if a user should be completely blocked from booking a conflicted Object, or not. The Permission will result in a Conflict message and NOT allow the user to continue and book the conflicting Object. The Conflict window will appear immediately.
The Permission can be found in the Modify User Window > Permissions > Advanced > "User Cannot Book Conflicting Object" Yes / No (default) and Web Permission Manager window > Web Profile > Events > "User Cannot Book Conflicting Object" Yes / No (default).
Other Settings > Toolbox > Settings > Server Setup
Resolve Surrounding Conflicts When Bookings Change: After resolving a Conflict the Booking Sub Status will be set to Confirmed automatically and does not have to be changed manually from the Conflict status to the Confirmed status (Hourline and Long Form).
Tasks Causes Conflicts: Controls if Task Bookings should conflict or not (default behaviour is to conflict).
Default Maintenance Causes Conflicts
By default a Maintenance booking causes a conflict, triggered by the "Conflict" checkbox on the Maintenance booking. If this is not wanted then you can change the behaviour so by default the "Conflict" is turned off.
Custom Personnel Event Types
For Custom Personnel Event Types you can
Inspect
From the Conflict window you can "Inspect" the conflict. This will filter the Object in the Hourline Tree.
Solving conflicts
Usually a conflict is solved by either manually replacing the conflicting booking with another resource or you can use the "Replace Conflicts With Available Class Members" option among others.
