Many improvements and bugfixes. Performance boost for mass updating reservations that do not need conflict checking.

‍

Features

• When updating a reservation, GoMeddo now only performs conflict checking if any field changed that is significant for conflict checking. So for example only changing the title of a reservation should not trigger conflict checking. This performance boost should be especially beneficial to clients using recurring reservations.
• GoMeddo now includes a Single Calendar Lightning component which can be placed on Lightning record pages. For the how-to article, see here .For an overview of available calendars, see here.
• It is now possible to disable progressive rendering on calendar views. Progressive rendering is when the calendar does not render reservations until the user scrolls to that part of the calendar. If you disable this, all reservations are rendered when the calendar loads, even before the user scrolls to them, but the calendar takes a bit longer to load.
• The Microsoft Outlook synchronization now allows you to map fields. To find out how, see here.
• Reservation conflict error messages now give more information about which dimension the reservation has a conflict in.
• The VisualForce calendars now remember the user’s last selected view. If the page is reloaded, this view will be selected instead of the default view as defined on the calendar.
• On the Lightning calendar, if there is only one reservation type, the reservation form will no longer show a dropdown to allow the user to select a reservation type.

‍

Bug fixes

• On views spanning more than one day, Predefined Timeframes with an empty value for Number of Days no longer interpret the empty value as if it was zero. This allows the user to define the number of days by selecting a time range of multiple days. For more info on Timeframes: take a look at our documentation.
• When a default Predefined Timeframe has an empty value for Number of Days, selecting a 24 hour period on the calendar no longer results in incorrect start and end times.
• The Resource form on the Resources & Types tab now correctly enforces FLS (field level security).
• Timezone conversion on the new Lightning calendar now also works correctly when your computer’s timezone does not match you user’s timezone in Salesforce.
• It is no longer possible to create duplicate Dimension Junction records.
• Dragging and dropping a reservation on the calendar now enforces update permissions and FLS for all records involved, including Dimension Junctions.
• Timeframe queries throughout the application now correctly enforce FLS.
• Clone and New Child actions in the dropdown menu in the left panel of the Resources & Type tree now also work in Microsoft Edge.
• The new Lightning calendar now passes the current view’s start and end times to any dynamic resource titles you have defined.
• The new Lightning calendar now correctly formats datetimes displayed in reservation titles. For more information on configuring reservation titles see here
• The Schedule calendar no longer shows an error message when trying to drag and drop a reservation template to another day. For more information on the Schedule calendar, see here.
• Removed the ‘Hide times without reservations’ and ‘Hide closed times without reservations’ checkbox fields on View that have become obsolete by the Column Hiding Behavior picklist introduced in version 4.40.

‍

Admin Actions

If you are upgrading, do the following to get the most out of thisGoMeddo release.

• Add the new checkbox ‘Disable Progressive Rendering’ to your View page layout(s).
• We are deprecating the GoMeddo Read Only permission set. This means that you can still use it, but we will not be updating it with new fields. Make sure your security model does not depend on this permission set being kept up to date.
• Check if you have translations for, or are referencing any of the following custom labels: CapacityExceeded, Capacity Exceeded Combined With Other Reservations, ReservationConflicts, Reservation Conflicts Without Times. These labels now have an additional merge parameter and you should review their usage.
• Delete the now obsolete checkbox fields ‘Hide times without reservations’ and ‘Hide closed times without reservations’ from the View object, unless your own solutions depend on these fields.

‍