GoMeddo version history archive
This page contains the version history before 2022
Version 4.74 November 15, 2021
Features
We implemented the logic that if you change fields that are not relevant to the recurring cycle of a reservation, we won't update all reservations in the same cycle.
We now support objects that don’t have a Name field (such as Case or Workorder)
You can now hide the recurring reservations section based on the reservation type that is selected.
Bug fixes
Improved the way in which outlook sync works, now it support once sync for multiple transactions
We fixed some missing permissions, specifically on the shared conflict checker logic that was introduced in the last release
Worked on the translations, includes new labels, new translations for existing labels
Allowing the Time Slot Picker to also work for other time zones than the user's timezone.
Fixed the currency symbol for multi currency orgs where the users currency is different from the records currency.
Fixed a bug so the status values in the picklist are correctly ordered.
Admin Actions
There is a new field on the reservation type “hide recurring section” please give your users access to this field and add it to the page layout.
There is a new field on Dimension that specifies the “Dimension Name Field”. Please give your users access to this field and add it to the page layout. The field should fallback to “name” as a value.
Version 4.73 September 29, 2021
This version brings a long awaited feature. Dimension Junctions will now conflict with Dimension Fields! This means that if you have related records will now conflict with direct reservations if you enabled the setting.
Features
Check conflicts on reservations using dimension junctions against other reservations on the same object
Support 'Display as link' for Related lists
Allow users to select record types when click 'New' from reservation form lookup
Custom Form Testing API runLookupOverrideSearch now works for any field searches (not only related lists)
Bug fixes
Labels and translations have been improved, not everything was translated as expected.
Fix reservation contact permission error when deleting a reservation without reservation contacts.
Admin Actions
(Optional) If you want to have shared conflict checking enabled you have to go into the dimension object and enable the “Use Shared Conflict Checking” checkbox. This will only work for dimensions that have both a related dimension field and a related dimension junction. You might need to add the field to the Dimension page layout.
Version 4.72 September 2, 2021
GoMeddo now supports four new languages, French, German, Spanish and Portuguese. We welcome any feedback on our translations!
We also include some nifty features that allow you to work better with GoMeddo in screen flows, especially the time picker. We also improved some of the filter options that are supported. Such as a LIKE filter or selecting multiple values within texts.
Our reservation form got an overhaul and now has support for field sets for collapsed related records:
Features
Four new languages are supported, French, German, Spanish and Portuguese
You can now unselect timeslots in your screen flows, allowing you to make even more user friendly flows.
The same component (for timeslots) can now optionally include a date field, which also improves the user friendliness of screen flows.
We now have the option to support multiple values in text and number filters.
The custom form API now has the option to fire OnBeforeSave events.
Bug fixes
Max length of Text fields and long text fields are now respected, also the decimal settings of number fields are now validated
There was an issue with unshared reservations that were not correctly displayed in the calendar. This has been resolved.
Version
4.71
July 8, 2021
Bugfix release to fix an issue introduced in v4.70 that would show Dutch translations to users that had their language set to a different language.
Bug fixes
Fixed a bug that would have certain dutch field and object translations appear if the users selected language was not dutch.
Version
4.70
July 7, 2021
In this release we have focused on a lot of improvements that allow the users and admins to better use GoMeddo in their day-to-day process. We included new functionalities for using GoMeddo with flows. Made functionality to expose a dimension as an ICal feed. We also improved the accessibility of GoMeddo.
Features
The standalone reservation form does now support a flow that can be run before loading the component. This allows you to set default values on the form. This flow has access to the Id of the record page the standalone form is loaded on.
When you wrap a reservation calendar you can now choose to make it “read-only” which would make the calendar display as normal, allowing the user to navigate and filter the calendar. But does not allow the user to create or edit reservations. See this page for documentation.
To improve the accessibility of the calendar, you can now set an ‘unavailability’ colour. The default grey will be overwritten by the colour you specify.
On the single month view we now indicate the current day in a different colour
Lightning filter dropdowns now always include a “None” filter entry allowing you to switch to no filter so you can see everything.
GoMeddo is fully translated to Dutch.
You can expose dimension(s) to be visible in an ICal feed. This allows you to subscribe to this feed via your calendars or via code. Documentation of this will follow.
You can now load The Time Slot Picker into a flow, allowing you to use this in your own custom screen flows and create your own process while utilising the availability and conflict checking of GoMeddo. See this page for documentation.
Bug fixes
We improved the support for multi-currency orgs in the new lightning components, which now copies the currency from the selected resource to the reservation or any related record.
Improved keyboard control voor lookups in the reservation form, now supporting up, down, enter and cancel.
Improved the real-time validation messages to no longer display null.
We include the “allow reservation deletion when updating a recurring reservation” check to the LWC calendar. This can be added to a permission set as a custom permissions.
Version
4.69
June 15, 2021
This release packages the two-way Google Calendar sync.
Features
We created a new extension package that allows you to sync any dimension you have with a Google Calendar.
We made sure that exisiting syncs (with Outlook) are not conflicting
Version
4.68
June 2, 2021
While this release was mostly focused on improvements and bug fixes there are some cool new features added as well. The real-time validation works even better than before! Also we updated the API to support services with their capacity.
Features
We added the “new record option” to the dimension junction search dropdowns so you can add new records from this dropdown as well.
Added a new REST endpoint /resources/*/services that allow for the retrieval of the remaining capacity of services for a resource.
More detail
The real time form validation on the LWC calendar will now trigger when any relevant field changes.
Allowed the B25.Util_PluginManager.DynamicResourceTitleData object to be constructed to allow for unit testing of DynamicResourceTitle implementations.
Improvements
The custom price calculation will attempt to get the fields it should trigger on from the same class as the calculation logic if no specific class is configured for triggering fields.
The dropdown clone and new child options on the Resources & Types page will now not be visible if the user does not have the permission to use them.
Fixed the saving of the reservation form when pressing the enter key on an input that should have other behaviour when pressing the enter key. For example text area fields now allow you to use enters again.
Changed the behaviour of the Display as Link field on Hover fields. The automatic displaying of lookup fields as links has been removed to allow for more control when deciding what fields should be displayed as links.
Bug fixes
Fixed the standalone reservation form not displaying on record and home pages when the page was being viewed on mobile.
Fixed long text formula fields not correctly wrapping the text.
Fixed Lookup dropdowns closing when you attempted to scroll using the scrollbar.
Fixed the next button not working on some view configurations.
Fixed Lookups in view mode showing data of a previously opened reservation if the field was empty on the selected reservation.
Fixed the timeslot picker not displaying errors when the creation of a reservation failed.
Fixed the timeslot picker not working if the selected reservation type did not have a fieldset selected. It now falls back on the B25__Custom_Fields fieldset.
Fixed reservation validation failures if the reservation ended at 24:00 and if the availability did not start at 00:00
Fixed reservations from previous views being passed to the Dynamic Resource title implementations on the LWC calendars.
Fixed an error that would cause the Resource tree to fail to load on the Resources & Types tab when the org contained more than 10000 resources.
Fixed an error that would appear if you attempted to create a new recurring reservation and you changed the dates of the reservation after opening the reservation.
Version
4.67
May 5, 2021
This is a big release that includes some nice features. For example, we now allow you to filter dimension-records based on a new filter in the top left. We have better support for mobile/communities with our stand-alone reservation form and we support multiple sections on the reservation form. Next to that, we squashed some bugs.
Improvements
The reservation form can now be loaded as a component on record pages app pages in a mobile app and in communities. Taking advantage of conflict checking and the functionality of the form without showing the whole calendar.
Added a new filter to the lighting calendar. This filter when you open it will add a checkbox to each dimension record in the calendar. You can then uncheck any of them and when you press the button again it will hide any resources you did not have checked. This is stored locally on the computer and is stored per user and calendar.
Soft conflicting dimension objects will now no longer be filtered out of lookups. They will now display but with a warning that they would result in a soft conflict.
You can now specify a comma separated list for the “Field set to use” field on Reservation type. When this is done each fieldset will create a section on the reservation form. This title of the section will be the label of the fieldset.
Bug fixes
Fixed a bug that caused the lightning form to ignore the B25__Skip_Subtotal_Calculation__c checkbox.
Fixed a bug that would cause availability checking to fail when a user with a different timezone than the user that created a reservation would update a conflict checking relevant field from the standard salesforce UI.
Fixed a bug that would cause the reservation hover to disappear if the hover would cause the page to get a scrollbar.
Added missing fields to the custom fields fieldset on resource.
Version
4.66
April 13, 2021
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.
Version
4.64
March 8, 2021
In this release, we fixed a number of bugs and implemented some improvements to make the overall user experience of the app better.
Improvements
Buttons permissions - Improved permissions on buttons to show only the buttons that you should have access to.
Filter Active Indicator - Added an active status to the button if a filter is active on the view
Formula field support Added better support for formula fields on the reservation form which are now displayed similar to the Salesforce formula fields.
Bug fixes
We fixed a bug that was caused by the Salesforce Spring ‘21 release which showed an error when opening the reservation form before the page was loading
We made sure that timezones don’t affect the display of time in the view mode of the reservation
We improved the default picklist value support on the reservation form that was not always triggering
We made sure that services are available for the user to see in the reservation form
We resolved a bug where the reservation title bar was not displaying correctly in a single month calendar
We made sure that checkboxes do not display a required asterisk
Version
4.63
February 26, 2021
This is an important version that fixes some major issues caused by the Salesforce Spring ‘21 release. It also contains some new features such as related lists on the reservation form, and updates to existing components and their availability in communities.
Admin Actions
If you are upgrading, do the following to get the most out of this release.
Add the new related list named ‘Related Lists’ to the Reservation Type page layout.
Features
Related Lists - It is now possible to add any kind of related list to the reservation form, this is no longer limited to dimension junctions: Link
Flow Buttons - It is now possible to have custom buttons run flows. This can be done through configuration or code.
Component Updates - The following components have a new property ‘Lookup to Dimension’ allowing you to set a related record as the dimension: Single Calendar, Multi Calendar, Time Slot Picker.
Community Components - The following components are now available in communities: Single Calendar, Multi Calendar, Time Slot Picker, Recurring Reservation.
Component Reference - With all the recent and projected development on the available components, we have decided to create a central reference for all the componentsdocumentation. For now only the calendar components have been documented there, the others will follow shortly.
Improvements
The ‘View in Salesforce’ link at the bottom of the reservation hover on the Lightning calendar now opens in a new tab instead of navigating away from the calendar page.
Bug fixes
The Salesforce Spring ‘21 release caused a major performance degradation, which has been fixed in this release.
The Outlook Settings tab on the GoMeddo Settings page was not visible even if the org had been configured correctly.
Fields on the VisualForce calendar reservation form, which were marked as required in the field set, were not being properly validated in the browser.
The ‘View All’ links under lists on the Settings page and the Resources & Types page now work again.
The loading spinner and greyed out area that appears when saving a reservation on the Lightning calendar now covers the entire form instead of only the top part.
Fixed an issue where the Time Slot Picker component would show additional incorrect time slots for certain time slot durations.
Version
4.61
December 3, 2020
This version brings a final much-requested feature from the VisualForce calendar to the Lightning calendar: Recurring Reservations. It also introduces a new component to quickly pick a timeslot and create a reservation directly from a record page.
Features
The Lightning calendar reservation form now displays a recurring reservation section if enabled on the settings tab.
There is a new component available for record pages, which allows users to select a timeslot and make a quick reservation for that record or its child resources. For more info take a look at our documentation.
Improvements
A new tab named “Lightning Calendar” has been included, showing the Resource calendar by default. The selected calendar can be changed in the Lightning App Builder.
Saving View records with a Slot Duration not conforming to a format of “0:00”, “00:00”, “0.00:00”, “00.00:00”, “month”, or “year” will now result in an error.
The Name field is no longer required for reservation templates on the Scheduler calendars.
The Lightning calendar now sets the default reservation type if defined on a resource type.
Bug fixes
The service section on the Lightning calendar reservation form no longer shows ‘Max null’ for services with an unlimited available quantity.
Fixed an issue with the custom ordering of View buttons on the Lightning calendar.
Fixed an issue where reservations on the single Lightning calendar with a buffer time had incorrect padding for their title text.
If the setting ‘Disable live update warning’ has been enabled, users will no longer get an error if the live updates PushTopic channel has been set to inactive.
Fixed an issue where the field ‘Dimension Allow Double Booking Field’ was not correctly responding to the value in the referenced field.
Both the VisualForce and Lightning calendars now trigger custom price calculations when ‘Services have a price’ has been enabled, even if ‘Resources have a price’ has been disabled.
Admin Actions
If you are upgrading, do the following to get the most out of this release.
This version will automatically update any View records with a Slot Duration of ‘30’ (which indicates 30 seconds) to ‘00:30’ (which indicates 30 minutes).
When upgrading, you might get the following error: Lightning_Calendar: In Lightning component B25:multiCalendarWrapper, property calendarId has an invalid value Resources. This happens if you have previously deleted the default calendar named ‘Resources’. To get around this error, simply create a new calendar named ‘Resources’ and try again.
Version
4.60
December 2, 2020
On top of some bugfixes and small improvements, this version finally brings a popular feature of the VisualForce calendar to the Lightning calendar: Custom Buttons. It also contains upgrades to the Lightning calendar filters, giving admins more fine-grained control and a new multi-select option to enhance the experience of their users.
Features
Just like the VisualForce calendar, the Lightning calendar now also displays Custom Buttons that have been configured in the database. Take a look here.
The Lightning calendar now allows buttons to be configured via Apex as part of the Custom Form Logic API. Take a look here.
Admins can now configure individual filter item properties of Lightning calendar filters. See our documentation.
Filter items now have a property that allows Admins to configure multi-selection on them. See our documentation.
Lightning calendars now allow you to define a different field to be used as the name for entries in a list on the reservation form. See the new field ‘Dimension Name Field’ on the Dimension Junction Display Setting object. See our documentation.
Improvements
A new setting has been added to the Settings tab to disable the ‘no hover definition’ message when hovering over reservations in a context for which no hover definition exists.
Our components that are available in the Lightning App Builder now have an easily recognizable GoMeddo icon, instead of the default Salesforce icon.
A new setting has been added to the Settings tab to enable the new ICU locale formats. Enable this setting if the “ICU Locale Formats” release update has been enabled in the org. For more information take a look at the Salesforce documentation.
Bug fixes
Lightning calendar filters on lookup fields no longer show only a subset of results in some cases.
The Lightning calendar now correctly sets the default Resource Layout, if one has been configured. For more information on Resource Layouts, see: our documentation.
The Timeframe dropdown on the reservation form now no longer shows Timeframes that are Resource or Resource Type specific, if no Resource has been selected. This applies to both VisualForce and Lightning calendars. For more info on Timeframes, see our documentation
Fixed a bug where selecting a Timeframe on the Lightning calendar reservation form did not update the reservation times.
Fixed a bug where changing the reservation times on the Lightning calendar reservation form did not update the selected Timeframe.
Fixed a bug where (custom) price calculations were not triggered and the (sub)total price was not updated in the pricing section when adding, removing, or modifying services.
Admin Actions
If you are upgrading, do the following to get the most out of this release.
Add the new ‘Dimension Name Field’ to your Dimension Junction Display Setting page layouts.
The ReservationContact object is now related to Contact through a normal lookup instead of a master-detail. The master-detail field will not be deleted from your org unless you remove it yourself. Any existing configuration still referencing the master-detail field (such as the default ReservationContact dimension junction) will continue to work until you remove the field.
The ReservationContact object is now related to Reservation through a normal lookup instead of a master-detail. The master-detail field will not be deleted from your org unless you remove it yourself. Any existing configuration still referencing the master-detail field (such as the default ReservationContact dimension junction) will continue to work until you remove the field.
Version
4.57
September 29, 2020
Besides a number of bugfixes, this version introduces record pages with calendars and makes calendar components deployable. This comes with an important caveat if you are already using calendar components, so make sure to check the Admin Actions below.
Features
Lightning calendar components now reference calendars by name instead of id. This has the major advantage that pages containing calendar components are now deployable between orgs.
Lightning record pages for Resource and Staff have now been included. These are identical to the default record Lightning calendar components, except that they include a Calendar tab with a Lightning calendar component.
It is now possible to create calendars without dimensions. This also means you can now easily add calendar components to objects without first having to create a dimension for them.
Bug fixes
The ordering of time headers on the Lightning multi calendar was incorrect. The ordering was exactly opposite of the VisualForce calendar. Also an order of ‘0’ (zero) was treated as if the value was ‘null’ (empty).
The 'Capacity' record type on Conflict has now been included in all permission sets.
The Reservation Status tab is now accessible through the B25 Admin permission set.
Currency and checkbox fields of records in a junction list were sometimes emptied when rerendering the VisualForce reservation form.
Ordering of junction lists on the Lightning calendar was incorrect.
The reservation form on the Lightning calendar did not validate a field as required if it was marked as required in the field set.
The ‘N/A’ option for filter fields on the Lightning calendar is now also supported by picklists.
Cells shorter than 1 hour caused incorrect hiding of cells.
The ‘View in Salesforce’ button in the Details section of the Resources & Types tab did not work properly.
Automated Booking Rule logic is no longer executed from the Opportunity trigger when the user has no access to the Automated Booking Rule object, or no Automated Booking Rules are configured in your org.
Admin Actions
If you are upgrading, do the following to get the most out of this release.
Important! Because calendar components now reference calendars by name instead of id, if you have included any components on your own pages, they will give an error message that the calendar can’t be found. To fix this, simply edit the page and re-select the correct calendar.
If you have wrapped any calendar components inside your own components, you will need to change the value passed into the calendar-id. This value should now be the calendar name instead of the id.
Check if your time headers on the Lightning calendar are ordered correctly. Configuring time headers is described here.
On install or upgrade, two dimensionless calendar config records will be created automatically. These have been included for convenience, so you can easily add calendar components on objects for which no dimension exists. Feel free to delete or modify these calendar records.
Version
4.56
September 11, 2020
This is a fairly large release with some bugfixes and improvements, in addition to a number of new features.
Features
The UI of filters on the Lightning calendar has been expanded for users without any permission to create filters. This allows users without permissions to have greater control over what they see, without the additional complexity available to users with permissions to create filters. For more on filters: take a look at our documentation.
It is now possible to configure buffer time before and after a reservation, for example to indicate setup and cleanup times. More information here: take a look at our documentation.
It is now possible to configure a flow to run when a reservation is being created on the calendar, before the reservation form opens. This can be useful to pre-populate fields with dynamic values, but flows are powerful and allow more complex use cases as well. For more information, see our documentation.
It is now possible to include junctions (such as ReservationContacts) or service reservations in the prototypeReservation when wrapping calendar components in your own components, as described in here.
GoMeddo now includes a dedicated home page in Lightning Experience, with reports and dashboards to give you more insight into your GoMeddo data. This home page (named ‘Home’) can be made available to your users if desirable: See Salesforce documentation.
Improvements
The Lightning calendar resource lookup now takes the reservation’s services into consideration, when showing available resources.
The Lightning calendar now shows a success message after saving a reservation.
The Lightning calendar reservation form now supports fields of the type Geolocation.
There is a new checkbox ‘Disable live update warning’ in the Details section of the Settings tab. Enabling this checkbox prevents users without PushTopic access from getting an error toast notification when loading the calendar.
Scheduler: the View lookup on Schedule now includes a filter that only shows Views of the ‘Schedule View’ record type.
‘View Record in Salesforce’ in the dimension context menu on the Lightning calendar now opens in a new browser tab instead of a Salesforce tab.
The Lightning single calendar now displays month views as a grid.
The Lightning calendar reservation form now respects the checkbox ‘Hide Selected Items From Search Results’ on the Dimension Junction Display Setting configuration object (this object is described here
After reloading or navigating, the Lightning calendar now scrolls to the current day/time on wide views (with a horizontal scrollbar), if the current day/time is outside of the visible part.
Bug fixes
Long names of resources (or any other dimensions) in the left hand column of the multi calendar are no longer cut off.
Fixed a bug where the ordering of fields in the hover popup were not always consistent.
Realtime calendar updates (through PushTopics) now work correctly on the Multi Calendar component available for record pages.
Reservation filters are now applied also to reservations that are only visible on the calendar because of their dimension junctions.
The ‘CustomFields’ field set on Service Reservation now includes the necessary fields for service reservations on the Lightning calendar to work immediately out of the box.
The Lightning calendar reservation form did not always trigger a price recalculation when the subtotal field or relevant service reservation fields were edited.
Admin Actions
If you are upgrading, do the following to get the most out of this release.
Since the Lightning single calendar now displays month views as a grid, check your single month view configurations.
Check if your Schedule views have correct slot durations. Recommended values are 1:00 for multi schedule views and 00:15 or 00:30 for single schedule views.
If you are running into installation problems due to not having permission to “change dashboard colors”, first make sure you have this permission and then try again. Salesforce knowledge article: https://help.salesforce.com/articleView?id=000349418&language=en_US&mode=1&type=1
Add these fields to your page layouts:
Reservation Buffer Color on the Reservation Color page layout
Reservation Start Buffer Size on the Reservation Type page layout
Reservation End Buffer Size on the Reservation Type page layout
Version
4.55
August 20, 2020
Major new feature 'Custom Form Logic' which allows the form to be customized using Apex.
Major Features
Custom Form Logic: this feature includes a complete Apex API to let you take programmatic control over the Lightning calendar reservation form. It will let you do things like calculate values, update fields, generate custom lookup results, and more. See the documentation section here.
Features
Like the VisualForce calendar, the Lightning calendar reservation form now includes a Services section when the selected resource has available services.
Like the VisualForce calendar, the default price calculation logic is now applied by the Lightning calendar reservation form when relevant fields are modified by the user.
Improvements
Intelligent Lookups on both the VisualForce and Lightning calendar reservation forms now clearly indicate when no results are found.
The Lightning calendar reservation form now falls back to the default ‘Custom Fields’ fieldset, if no fieldset has been entered on the Reservation Type.
Reservation Types showing up in the dropdown at the top of the Lightning calendar reservation form are now properly left-aligned.
The B25 Community permission set now includes basic access on the Conflict object, so that community users will not fall back to hard conflicts when you have soft conflicts configured.
Bug fixes
The filters defined on the VisualForce calendar no longer cause ‘Field is not accessible in this context’ errors due to an outdated API version.
After deleting the last dimension or reservation filter on the Lightning calendar, the list is now cleared correctly.
The Lightning calendar reservation form no longer crashes under specific circumstances with a dependent picklist on the form.
Version
4.52
June 22, 2020
Smaller release with an improvement to the new filter UI and a few bugfixes.
Features
The filter UI on the Lightning calendar now supports editing existing filters. This allows you to change a filter from personal to global, or to edit which things other users can override (such as values and operators).
Bug fixes
Inaccessible reservation title fields are now hidden on the Lightning calendar instead of causing an error.
Fixed an issue on the Lightning calendar, where if the reservation sObject had multiple record types, saving a reservation would fail with an ‘unable to read sObject’ error.
Leaving the Calendar field blank when creating a Resource Title now gives a helpful error message instead of a cryptic one.
Version
4.51
June 12, 2020
Some bugfixes and smaller improvements, as well as some new properties on the calendar components to control the view, start date, and prepopulated reservation fields.
Features
The single and multi calendar components now have API properties that let you control the start date, the displayed view, and the prepopulation of reservation fields. Note that these are API properties and not page builder properties, so they are only accessible when wrapping these components inside your own custom components. More information here.
The MultiSchedule calendar component now displays a context menu when clicking on the dimensions, just like the Lightning and VisualForce multi-row calendars do.
The Lightning calendar now prompts the user with a confirmation dialog when clicking Delete on the reservation form.
The option to create global filters is now disabled if the user has no permission to create global filters.
Bug fixes
The previous version contained a conversion script that would automatically generate JSON for the new filters, based on your existing filters on the VisualForce calendar. However that script contained a bug causing the conversion to be incorrect. This bug has now been fixed, and if an incorrectly converted filter is detected that filter will be corrected by the upgrade process.
Fixed a bug where the Lightning calendar would sometimes give the following error on refreshing: [Cannot read property 'x' of null]
Fixed a bug on the Lightning calendar where the order of fields in the reservation hover window would be reversed compared to their order on the VisualForce calendar.
The Lightning calendar no longer crashes when the configured reservation title group contains no titles.
The filter item modal no longer gets hidden behind the other filter panel if you have both filter panels open.
Fixed a bug where the Lightning calendar would not correctly display unavailabilities, (availability records that have the checkbox ‘Unavailability’ checked).
Admin Actions
If you are upgrading, do the following to get the most out of this GoMeddo release.
Confirm that your ordering of hover fields is correct after upgrading, because these have been reversed for the Lightning calendar as part of a bug fix. More info on configuring hover fields here.
Version
4.50
May 10, 2020
On top of some bugfixes and small improvements, this version finally brings a popular feature of the VisualForce calendar to the Lightning calendar: Custom Buttons. It also contains upgrades to the Lightning calendar filters, giving admins more fine-grained control and a new multi-select option to enhance the experience of their users.
Features
Just like the VisualForce calendar, the Lightning calendar now also displays Custom Buttons that have been configured in the database, see our documentation.
The Lightning calendar now allows buttons to be configured via Apex as part of the Custom Form Logic API: Take a look at our documentation.
Admins can now configure individual filter item properties of Lightning calendar filters. See here.
Filter items now have a property that allows Admins to configure multi-selection on them. See: our documentation.
Lightning calendars now allow you to define a different field to be used as the name for entries in a list on the reservation form. See the new field ‘Dimension Name Field’ on the Dimension Junction Display Setting object: in our documentation.
Improvements
A new setting has been added to the Settings tab to disable the ‘no hover definition’ message when hovering over reservations in a context for which no hover definition exists.
Our components that are available in the Lightning App Builder now have an easily recognizable GoMeddo icon, instead of the default Salesforce icon.
A new setting has been added to the Settings tab to enable the new ICU locale formats. Enable this setting if the “ICU Locale Formats” release update has been enabled in the org. For more information see the Salesforce documentation
Bug fixes
Lightning calendar filters on lookup fields no longer show only a subset of results in some cases.
The Lightning calendar now correctly sets the default Resource Layout, if one has been configured. For more information on Resource Layouts, see our documentation.
The Timeframe dropdown on the reservation form now no longer shows Timeframes that are Resource or Resource Type specific, if no Resource has been selected. This applies to both VisualForce and Lightning calendars. For more info on Timeframes, see our documentation
Fixed a bug where selecting a Timeframe on the Lightning calendar reservation form did not update the reservation times.
Fixed a bug where changing the reservation times on the Lightning calendar reservation form did not update the selected Timeframe.
Fixed a bug where (custom) price calculations were not triggered and the (sub)total price was not updated in the pricing section when adding, removing, or modifying services.
Admin Actions
If you are upgrading, do the following to get the most out of this release.
Add the new ‘Dimension Name Field’ to your Dimension Junction Display Setting page layouts.
The ReservationContact object is now related to Contact through a normal lookup instead of a master-detail. The master-detail field will not be deleted from your org unless you remove it yourself. Any existing configuration still referencing the master-detail field (such as the default ReservationContact dimension junction) will continue to work until you remove the field.
The ReservationContact object is now related to Reservation through a normal lookup instead of a master-detail. The master-detail field will not be deleted from your org unless you remove it yourself. Any existing configuration still referencing the master-detail field (such as the default ReservationContact dimension junction) will continue to work until you remove the field.
Version
4.49
April 29, 2020
This release contains an important bugfix for the new Lightning calendar.
Features
The global setting ‘Show greyed out blocks on the calendar for unshared reservations’ is now also supported on the new Lightning calendars.
Bug fixes
Fixed a bug where the new Lightning calendar would sometimes give an error when clicking outside of it, like closing another tab for example.
The vertical and horizontal lines on the calendar now no longer disappear at certain browser zoom levels.
Fixed the validation logic giving an error when updating multiple reservations, where one or more had their status or type changed, and one or more that did not have their status or type changed.
Internal logic will now give a more meaningful error message containing the resource id if it can’t find that resource’s materialized path.
Version
4.48
April 10, 2020
Many improvements, mostly to the new Lightning calendars.
Features
GoMeddo now includes a Multi Calendar Lightning component which can be placed on Lightning record pages, to display the children of that record. For the how-to article, see here For an overview of available calendars, see here.
There is a new checkbox property ‘Show Availabilities’ on the Multi Schedule component. When enabled, any relevant availabilities with the checkbox ‘Include On Scheduler’ set to true will be loaded and shown to the user. When disabled, every row shows as always open. This property is enabled by default. For more information: see here.
The Lightning calendar now remembers the user’s last selected view when the page is reloaded.
The Lightning calendar now respects the ‘Prompt before moving’ and ‘Prompt before resizing’ checkboxes that have been configured on the calendar configuration record.
Links on the Lightning calendar now open a new Salesforce tab or a new browser tab instead of navigating away from the calendar.
The Lightning calendar’s reservation form now also has a view mode, as opposed to only an edit mode.
The Lightning calendar’s reservation form now hides the Pricing section if the global setting ‘Resources have a price’ has been disabled.
The resource lookup on the Lightning calendar’s reservation form now also searches in the resource’s context (parent and grandparent names, as shown between parentheses in the results).
Controlling and dependent lookups and picklists are now supported on the Lightning calendar’s reservation form.
Admins can now configure the height of Lightning calendar components using the new ‘Max height’ property.
The picklist property ‘Calendar’ on the Single Calendar component will now only show valid calendar records. Valid records are Calendars of the ‘Single’ record type, linked to a Dimension that is of the same object type as the record page that you want to add the component to.
Bug fixes
Reservation titles on the Lightning calendar would break if they were cross object references (like B25__Resource__r.Name).
The alignment of reservation titles on the Lightning calendar was incorrect for reservations that started before the current view started.
The Lightning calendar no longer breaks when Dynamic Dimension Groupings include a ‘None’ option. For more information on Dynamic Dimension Groupings, take a look here.
Dynamic Dimension Groupings on the Lightning calendar now show the record name instead of the id, if the grouping field is a lookup.
Dimension junctions that the user does not have read access to are now hidden on the Lightning calendar’s reservation form, instead of throwing an error.
If the user does not have create access on the Reservation object, the reservation form on the Lightning calendar now simply does not open, instead of throwing an error.
The search results for lookups on the Lightning calendar’s reservation form are now consistent with the VisualForce calendar.
Version
4.47
March 31, 2020
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.
Version
4.46
March 16, 2020
This release contains a major feature in the form of a new calendar built entirely as a Lightning Web Component.
Major Features
This release contains a new version of the calendar as a Lightning Web Component (LWC). Rebuilding the calendar as a LWC should have a notable positive impact on calendar performance. It also opens up possibilities of easily integrating the calendar into your own Lightning solutions. Not all features of the current calendar are supported yet, but most of them will be added in later versions. Feel free to reach out to us for specific requests. For an overview of the differences between the calendars, see here.
Minor Features
The Dimension and Reservation Template filters on the Schedule calendars have been upgraded to support condition groupings and ‘and/or’ constructions.
Admin Actions
If you are upgrading, do the following to get the most out of this GoMeddo release.
If you want to get started with the new Calendar LWC, see here.
Version
4.45
March 2, 2020
Minor performance boost for a specific endpoint and a bugfix for the Outlook sync.
Features
Minor performance boost to the Available Time Ranges. get Time Ranges global Apex method.
Bug fixes
Fixed an issue where the Outlook sync to Salesforce would fail if a nextlink was returned.
Version
4.44
February 21, 2020
One minor UX improvement and a critical bug fix for clients using the Recurring Reservation component.
Features
All search inputs in the GoMeddo UI now follow the official Salesforce Lightning design system.
Bug fixes
Fixed the Recurring Reservation component being broken by the Salesforce spring update.
Version
4.43
February 14, 2020
One minor feature and two bugfixes.
Features
-When creating a new Reservation Type, it now automatically gets linked to every existing calendar. When creating a new Calendar, every existing Reservation Type now automatically gets linked to it.
Bug fixes
Checkbox fields in related lists on the reservation hover now display checkboxes instead of the text ‘true’ or ‘false’.
On the Reservation form, new services or related records added to a reservation now populate the default field values defined in Salesforce.
Version
4.42
February 6, 2020
Bug fixes
When hovering over a Reservation on the Calendar, checkbox fields are now displayed as read-only checkboxes instead of the text ‘true’ or ‘false’.
Fixed null pointer exception when not providing start/end time parameters to the {resourceId}/availability endpoint. An invalid parameters response is now returned instead.
You can now delete resource types that have no related resources. Virtual resources are now ignored and are automatically deleted when deleting the resource type.
The Name field on the resource form now enforces the required attribute.
Fixed availabilities not loading if grouping was enabled on a calendar and there were not enough dimension records to form a group.
Fixed the calendar not correctly updating when pushtopics were disconnected and a Recurring Reservation was destructively updated.
Fixed the Resource Type save button sometimes not triggering after updating the Resource Type name.
The Available Time Ranges .get TimeR anges global method now assumes that a null value for the reservation parameter means no fields on Reservation have an effect on conflict checking instead of throwing a null pointer exception.
Improved error messages when creating invalid Outlook sync connections.
Fixed the date picker on the calendar not navigating to the correct date if your timezone was GMT+1 or higher.
The small colored legend for the reservation statuses in the calendar filter has been removed. This was done because the shown colors were either invisible or wrong. Because of the flexibility of the GoMeddo coloring system it is not currently possible to generate an accurate and usable legend.
Switching between Resource(Types) on the Resource & Types tab now blocks user interaction to prevent unexpected results from actions performed by the user while the page was loading.
Fixed the Resource(Type) tree context menu actions (‘new child’ and ‘clone’) not working if no Resource(Type) was selected.