In this release we mainly focused on improvements and bugfixes. We now show better conflict notifications and give you the option to hide your services from the form if you don’t want them.
‍

Admin Actions

• Add the new Hide Service Section field to the reservation type layout
  
  
• Add the Prevent Horizontal Drag and Prevent Vertical Drag to the Multi Resource Calendar Layout.
  ‍
• Add the Display as Link field to the Hover Field layout
  ‍
• Add the Display as Link field to the Related List Field Layout.
  ‍

Improvements

• Added support for the Prevent Horizontal Drag and Prevent Vertical Drag on the lightning calendar.
  ‍
• Added a No related records message in the dropdowns of the related lists on the reservation form on the lighting calendar.
  ‍
• Added a soft conflict toast notification if you save a reservation through the reservation form on the lightning calendar.
  ‍
• Added a setting Hide Service Section on reservation type that allows you to hide the service section based on what reservation type a reservation is.
  ‍
• Soft conflict notifications on the visualforce calendar now behave the same as hard conflict notifications.
  ‍
• Added new settings to Hover Fields and Related List fields on reservation hover Display as Link This setting will force a field to render as a link. Name and Id fields are rendered as a link by default as long as they are on a related sObject.
  ‍

Bug fixes

• Fixed a bug that would cause the search in the tree on the Resource & Types tab to occasionally hang.
  ‍
• When Outlook synchronization is enabled the recurring reservation component will create reservations synchronously instead of asynchronously to prevent conflicts with the Outlook synchronisation.
  ‍
• Fixed a bug that would cause the default time frame to not always be selected when opening the form.
  ‍
• Fixed a bug that would cause certain form functionality to not work when a default reservation type was selected on the resource type. Most noticeably reservation buffers.
  ‍
• Fixed a bug that would cause a SObject row was retrieved via SOQL without querying the requested field error when saving a dimension junction without any conflict checking configured.

‍