Page Comparison

...

Excerpt

Version 5.9 -September 19th, 2023

Features

Conflict Rules allow you to fully enforce your business logic on reservations which are being made using GoMeddo. This makes sure only reservations can be made, which are allowed.
You can use any data on the reservation itself, related records and data on the resource, staff, availability or anything you’re booking and in your rules, allowing for endless possibilities. You can even use the permissions of the user, trying to make the reservation. It’s also possible to give detailed feedback to the users trying to make the reservation, why something is not allowed or why they’ll get a warning. As it’s a new feature we will not yet automatically activate this for you, if you want to check it out, see our documentation.

Bugfixes & Improvements

It’s now possible to change only future occurences of your recurring reservations
We’ve added multi picklist filtering, to make it easier to select multiple items
Fixed an issue with unavailability not being displayed on the staff calendar.
Fixed an issue with the realtime validations and when a related record was not shared with the user trying to make the reservation.
Fixed a few issues with Daylights savings and recurring reservations.
Fixed an issue with the availability endpoint and timezones
Upgraded the API version from 54 to 56
Fixed a bug where the mobile calendar didn’t load anymore.

Admin actions

A bug was fixed in the https://apidocs.gomeddo.com/#/availability/post_availability availability endpoint when the timezone was shown in GMT while it was not (only for non resource dimensions). All results are now correctly indicated in GMT based on the timezone of the integration user. If you adapted your integrations earlier to compensate for this behaviour, take a look at the new results. If you integration user was already set to GMT, nothing changed.

...

Features

Conflict Rules allow you to fully enforce your business logic on reservations which are being made using GoMeddo. This makes sure only reservations can be made, which are allowed.
You can use any data on the reservation itself, related records and data on the resource, staff, availability or anything you’re booking and in your rules, allowing for endless possibilities. You can even use the permissions of the user, trying to make the reservation. It’s also possible to give detailed feedback to the users trying to make the reservation, why something is not allowed or why they’ll get a warning. As it’s a new feature we will not yet automatically activate this for you, if you want to check it out, see our documentation.

Bugfixes & Improvements

It’s now possible to change only future occurences of your recurring reservations
We’ve added multi picklist filtering, to make it easier to select multiple items
Fixed an issue with unavailability not being displayed on the staff calendar.
Fixed an issue with the realtime validations and when a related record was not shared with the user trying to make the reservation.
Fixed a few issues with Daylights savings and recurring reservations.
Fixed an issue with the availability endpoint and timezones
Upgraded the API version from 54 to 56
Fixed a bug where the mobile calendar didn’t load anymore.

Admin actions

A bug was fixed in the https://apidocs.gomeddo.com/#/availability/post_availability availability endpoint when the timezone was shown in GMT while it was not (only for non resource dimensions). All results are now correctly indicated in GMT based on the timezone of the integration user. If you adapted your integrations earlier to compensate for this behaviour, take a look at the new results. If you integration user was already set to GMT, nothing changed.

Bugfixes & Improvements

...