Skip to content

Global Schedule Settings

Tip

To access these settings, you will need to be in a group that has access to the Admin Module

These are global schedule settings (settings that affect all schedules and all users) and are located under Admin -> Module Settings -> Schedule -> Schedule Settings.

Realtime Updates on Schedule (BETA)

Yes / No
Default = No

Warning

This feature is still in BETA, use with caution and please report any issues.

When this option is set to Yes the schedule will automatically show new bookings and changes to existing ones in realtime, without having to refresh the page.

In addition to enabling this feature, you must also have full access to the schedule and all its bookings to actually see the "Realtime Updates" load on the schedule.

Required Resources

Yes / No

Default = No

When this option is set to Yes, bookings are required to have at least one resource set before validation will pass and the booking is saved to the server.

Required Status

Yes / No

Default = No

When this option is set to Yes, bookings are required to have at a status set before validation will pass and the booking is saved to the server.

Show Week Numbers

Yes / No

Default = No

When this option is set to Yes, week numbers are shown on timeline views.

Disable Clash Detection

By default, FoxOMS will alert you anytime a booking conflicts with another on a certain resource.

For example, if I try and create two bookings in Edit Suite 1, I will receive the following warning.

Booking Clash

In some instances, however, it may be perfectly acceptable to have two bookings occur at the same time. You can choose which resource types (if any) you wish to exclude from clash detection. Hold down SHIFT to select multiple options and ALT to de-select.

Note

This setting only disables the clash alerts, bookings that clash will still have red cells in the timeline views

Disable Clash Detection

In the above example, any bookings that clash with resources with a type of "Room" or "Equipment" will not trigger a booking clash alert.

Show All Bookings on the Calendar

Yes / No

Default = Yes

Note

This setting only affects the calendar views, the timeline is unaffected as the timeline can only ever display bookings directly related to resources.

By default, all bookings are displayed on the calendar, regardless of whether the bookings have any links to the resources specified under Admin -> Schedules.

The biggest advantage of this mode is that it allows bookings without any resources to be created and displayed.

However this mode can become problematic if you have lots of schedules, lots of resources and lots of bookings that don't relate to their schedules.

Its' also recommended to change this setting to No, if you are limiting access to schedules to certain users / groups, to avoid unrelated bookings still being accessible by the calendar and grid views.

By selecting 'no', only bookings that have a corresponding resource are shown on the calendar.

Resource Color Priority

Enabled / Disabled

Default = Disabled

Bookings with multiple resources displayed on the timeline views are able to correctly show the resources, in their correct colors, because each resource represents it's own 'block'.

Multiple Resource Booking Timeline

However, when the calendar views condense multi resource bookings into a single block, a generic 'blue' color is displayed, indicating that there are multiple resources behind the booking.

Multiple Resource Booking Calendar Default

It is possible to override this behaviour by adjusting the Resource Color Priority setting to Enabled. You can then adjust the color priority of the various resource types.

Multiple Resource Booking Timeline

Now the calendar displays the 'green' color of the person resource, because it takes priority over the equipment resources.

Multiple Resource Booking Calendar Priority

Everyone can View Bookings Linked to Private Projects

Yes / No

Default = Yes

FoxOMS projects are able to be 'private', which means that the contents of those projects can only be seen by administrators and people who have been given access.

Many people are surprised to discover then, that (by default) bookings created on private projects are in fact visible (read only) to everyone who has access to the schedule.

The reason for this is actually quite simple. If bookings are hidden, it becomes very difficult to schedule resources with confidence that they are actually available. There is a real possibility that double bookings will occur.

If the risk of double bookings is acceptable, you can change the setting to No, which will hide bookings linked to private bookings from the schedule.

Restrict Editing of Bookings

Yes / No

Default = No

Prevents user Jane from editing or deleting Bob's bookings and vice versa. Jane can continue to edit or delete her own bookings. Administrators still have global permissions.

Useful in larger organisations where you have a lot of staff accessing the schedule and you want to prevent the accidental or intentional editing or deletion of other staffs bookings.

Booking Label Template

- [ PROJECT_SHORTCODE ] + BOOKING_NAME + [ PROJECT_NAME ]
- BOOKING_NAME + [ PROJECT_NAME ]
- [ PROJECT_NAME ] + BOOKING_NAME
- [ PROJECT_NAME ] + CLIENT_NAME
- PROJECT_SHORTCODE + _ + PROJECT_NAME + _ + BOOKING_NAME + _ + CLIENT_NAME

Default = [ PROJECT_SHORTCODE ] + BOOKING_NAME + [ PROJECT_NAME ]

Allows customisation of the data shown within all booking titles shown on the schedule. This option does not affect calendar feed output.